-
Notifications
You must be signed in to change notification settings - Fork 482
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
ci: release without committing to main branch #1434
Conversation
Committing to the master branch isn't allowed from github actions because of our branch protection rules. There's no easy way to allow github actions to bypass this. As a workaround, skip all the parts of the release that needed to commit to the repo. This means moving the version config to an environment variable, which shouldn't be an issue.
af75b87
to
cd229d2
Compare
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.
thanks for figuring this all out! Feel free to ack/ignore all these since they're all optional!
Co-authored-by: Jonathan Zacsh <[email protected]>
576c3d7
to
cc4c986
Compare
Co-authored-by: Jonathan Zacsh <[email protected]>
cc4c986
to
1996285
Compare
Thanks for the suggestions! Applied them all |
Hey @calumcalder if I understand this latest tag correctly, then it:
Is that kind of bump what we want? Or would we expect just a patch bump for a commit like this? (ie: do we want it to have done - NEW_VERSION=$(cz bump --get-next) || exit 1
+ NEW_VERSION=$(cz bump --get-next --increment-mode PATCH) || exit 1 |
@jzacsh The bump from 1.0.4 to 1.1.0 was intentional - it calculates it from the difference between HEAD and the previous tag, and there have been a lot of commits between v1.0.4 and now, including some |
Committing to the master branch isn't allowed from github actions because of our branch protection rules. There's no easy way to allow github actions to bypass this.
As a workaround, skip all the parts of the release that needed to commit to the repo. This means moving the version config to an environment variable, which shouldn't be an issue, and using git tags as the source of truth.