-
Notifications
You must be signed in to change notification settings - Fork 406
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
chore: allow updating stage0 via workflow_dispatch #3052
Conversation
|
.github/workflows/update-stage0.yml
Outdated
@@ -23,16 +24,17 @@ jobs: | |||
- uses: actions/checkout@v3 | |||
with: | |||
ssh-key: ${{secrets.STAGE0_SSH_KEY}} | |||
- name: Check if update is needed | |||
- run: echo "DOIT=yes" >> "$GITHUB_ENV" |
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'm not super excited that the flag is named DOIT
here!
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.
Happy to change, any suggestions?
(Is DOIT somehow culturally inappropriate in a way I didn't see, or otherwise not good?)
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.
Is should_update_stage0
better?
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.
Just unclear. (I have a vendetta against 'it'.)
Could we have a paragraph somewhere (not quite sure the best place? dev guide in the manual?) explaining how to invoke this via |
Good idea, will do. The bootstrapping section of the manual probably |
I changed the flag, and also rewrote the section on updating stage0 in the manual, PTAL |
follow-up to #3042