-
Notifications
You must be signed in to change notification settings - Fork 47
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
Automated Branch Protection Detection #43
Comments
Hey @paulmowat , First of all thank you for using my github action. So your usecase If I am right is, directly committing by changing with personal token. I think I did suggest it in my readme regarding this. So a way to disable protection detection So how about an option like |
Yes, that's it. I set up branch protection to allow a specific build user to commit and create a personal token for that user. A option to turn off the protection to avoid it creating the PR would do the job. Could do Happy to do a PR for the change if your ok with that some point this week 😄 |
Oh sure. You can raise any concerns regarding this here. I am happy to help anytime. Just adding a walkthrough here.
|
Hey @paulmowat first of all apologizing early. Now the reason, I ended up implementing this while releasing for another patch. I thought you may have got busy with work, so thought let me solve it on the fly. If I made you efforts in vain, so sorry Closing this issue as this will resolve it. If not or if you have any trouble feel free to open the issue. |
Hi,
Just started using this and wanted to use this along with branch protection.
I noticed a recent change to automate detection of this and to raise a PR instead of doing it automatically.
It is possible to have branch protection and set up appropriate personal access tokens that you could pass instead of the GITHUB_TOKEN to allow it to work.
I have this working on v2.3 with a branch setup with branch protection and the is_protected option set to false (to avoid PR creation) and it updates fine.
It would be good to still have ability to set is_protected to override the automated logic for above scenario.
Thanks
Paul
The text was updated successfully, but these errors were encountered: