Clik here to view.
Best practices for protected branches
Branch protection is part of a powerful set of configuration options that give repository administrators the ability to enforce security policies by preventing accidental branch deletions, enforcing...
View ArticleBest practices for protected branches
@pierluigi, I’m interested in this particular idea: " Do: use this option as a way to bypass pull request based worfklows for those bots or other apps that need to be granted permissions to push...
View ArticleBest practices for protected branches
Hi @cobrabr thanks for the comment. Please note that: The ability to restrict branches is a type of branch protection that’s available for public and private repositories owned by organizations in...
View ArticleBest practices for protected branches
Yeah, I know where to do it, but I don’t know how to use it to bypass the PR workflow, as you suggested. If I turn it on in the same rule in which I enable Require pull request reviews before merging...
View ArticleBest practices for protected branches
@pierluigi I have a similar question to @cobrabr . I really want to enable “Require status checks to pass before merging” but I only want it to affect PRs. I want all users to still be able to push...
View ArticleBest practices for protected branches
Hi @pierluigi I have the same question as @cobrabr, I need to give permission to a specific account to be able to push to the master branch without having to do a PR since it’s all executed during a...
View ArticleBest practices for protected branches
@pierluigi Adding my voice to the others here. There does not seem to be any way to just exclude a user/app from the checks. Being able to have CI commit a version bump to the main branch seems like a...
View ArticleBest practices for protected branches
Hi @dblanchette @rlejeune @evhaus @cobrabr – the easiest way to allow merging PRs while bypassing required checks would be to leave the “include Administrators” flag unchecked – that allows users with...
View ArticleBest practices for protected branches
Thanks for the detailed answer! Unfortunately it does not work for us: We cannot give Admin access to a bot user because that means we would need to share that user’s personal access token with all of...
View ArticleBest practices for protected branches
Hey there – I recommend getting in touch with our Support team as they can better understand your specific request and help you find a solution that works for your needs: https://support.github.com...
View ArticleBest practices for protected branches
I’m a bit late to the party, but I have been dealing with the same issue. I ended up unchecking “enforce admins” and creating a service account as the only user with admin rights. I then shared the...
View ArticleClik here to view.
Best practices for protected branches
Good afternooon, Can I please request clarity on the following: Require status checks to pass before merging If you test your code with a continuous integration system that sends build statues back to...
View ArticleBest practices for protected branches
What “role” has an deploy key when given write access? When i protect a branch, by default it says on push can be done by " Organization administrators, repository administrators, and users with the...
View ArticleBest practices for protected branches
To anser my own question, deploy keys seem to have an Admin role. as described in Managing deploy keys - GitHub Docs And by having the team members as maintainers, a protected branch, and only allow...
View Article