Closed drodarie closed 3 months ago
The GitHub App seems like the more appropriate solution :) You can name it the Automatic Release Bot
and add it to the bypass list.
Ok I have a working solution (it was a tricky one), here are the changes I suggest that:
dbbs-lab
which will have write permissions on bsb-core
or any repository from the organization. This app should have a private key that we can use to access it. bsb-core
or all repos from dbbs-lab
.bsb-core
: use rulesets
instead of the default branches
protection system (technically does the same but allow certain users and app to bypass rules). I struggled a lot but I finally have a working version on my test repo
organization level or repo level
org level seems better?
we change the branch protection rules on bsb-core: use rulesets instead of the default branches protection system (technically does the same but allow certain users and app to bypass rules).
yea, they're a new feature from this year, switching is good :)
Seems like a good solution, let's do it.
Because of the protection on the main branch the automatic release pipeline does not work. In short, the github bot is not allowed to push on main. https://github.com/orgs/community/discussions/13836
There are no clean solution but there are two workarounds:
I am not sure which one is the best option..