-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(archiving): Automate workflow updates #2317
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a lot of sed
commands in here! Some (many?) of them could be combined, but I left each step separate, as I think it more clearly lays out what needs to happen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like how you organized this with the comments, steps, and including individual sed
commands. It makes something that could otherwise be really difficult to read (as a human) much more digestible.
Looking at how many steps you've automated along the way is super cool too! 👏
Great work here @pepopowitz!
Oh I forgot to mention that chatGPT helped me with many/most of these It did get some things wrong....but it was much more helpful than harmful. |
So generous of you to give credit where credit is due! |
Description
Part of #1173.
This PR automates the CI workflow updates involved in archiving an unsupported version.
See the changes in https://github.com/camunda/camunda-platform-docs/pull/2235/files, specifically within the
.github/workflows
folder, for a snapshot of all the changes included in this automated step.When should this change go live?
hold
label or convert to draft PR)?PR Checklist
/versioned_docs
directory, or they are not for an already released version./docs
directory (aka/next/
), or they are not for future versions.