-
Notifications
You must be signed in to change notification settings - Fork 252
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
Version bump failed on protected branch #156
Comments
I imagine you have a private Github Token, if that is the case, try this:
The secret is the |
@leandrooriente does not work.
|
I'm having this same issue in one repo, but not another. Same token, same action setup. It works in one repo, but fails with this same error in another. Any ideas? I'm using the latest version of the action, but have tried several of the past releases to no avail. |
Having same issue with this action, tried to add |
When adding |
I found this action which can push to protected branches by using a personal access token: https://github.com/CasperWA/push-protected |
For support "The protection rule is set up on pull request." I think the action should support option to create pull request instead of direct commit. |
we fixed by just throwing it all out of the window and building from first principles thinking.
Here's the link to the workflow So whenever you need to update a major or a minor version you could just manually do it (I am assuming you will be doing them on a monthly/quarterly basis, and if you are someone who's updating it more frequently than this, kudos mate! |
I have set up a branch protection rule to run a few simple unit tests before code is merged. However, once the rule is enabled, I am having issue using the version bump. Here is the error messge in github action:
✖ fatal remote: error: GH006: Protected branch update failed for refs/heads/main.
remote: error: 2 of 2 required status checks are expected.
Any idea on how to resolve this?
The protection rule is set up on pull request.
Thanks
George
The text was updated successfully, but these errors were encountered: