You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon researching, we found an issue with the current branch protection rules. The naming specification for the branch protection rules (In GitHub, under Settings->Branches), was not picking up all of our branches. As of the screenshot below, there were 34 branches in our repo, but the rules applied to only 14.
The rules use fnmatch (unix filename pattern matching), so "*" does not pick up any branches with a "/" slash in the name, as most of our branches use. Changing the catch-all pattern to "/" resolves this issue:
Secondly, all of us on the TI team were still able to push unsigned commits (to branches other than main) since we are all repo admins. The "Do not allow bypassing the above settings" option within the rule also needs to be checked. Without it, there's no warning or indication that we're pushing an unsigned commit.
DevEx/OpEx
One possible option is to add a pre-commit hook
Tasks
Additional Context
https://flexion.slack.com/archives/C055XTF22B0/p1727721609331709
The text was updated successfully, but these errors were encountered: