-
Notifications
You must be signed in to change notification settings - Fork 16
feat: Add a release job to generate code on release PRs GH-66 #110
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
Conversation
c98a07b to
1567bcb
Compare
229ee18 to
2ad85dc
Compare
f1752f4 to
05356de
Compare
| echo "Generate did not cause any changes to the code. OK to proceed with the release" | ||
| else | ||
| echo "Generate updated the code. Committing the changes..." | ||
| git config --global user.email "$GITHUB_ACTOR@users.noreply.github.com" |
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 this safe? Would this be an unverified commit?
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 sure what kind of commit it would be. I think it is verified. The github action takes on the permissions of the actor that initiated that action.
jackwotherspoon
left a comment
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.
LGTM, however I think we should maybe double-check with the Github Automation team before merging if they have a best practice for pushing code from a Github Action as well as if there is any known issues with doing so from the release-please app's bot user.
After release-please opens a PR, generate the code so that the final release version stored in version.txt
is properly reflected in the generated code.