Closed Schievel1 closed 2 years ago
This is limited by default but krypton simply gave him access to this repo after he asked. I have removed his maintain access for now
No, I actually did not mean him in particular.
Github has the option to protect the main branch. Then you can not push to main, always need to merge a branch to move commits into main. Can you set this up?
Ah, you mean the protection rules in general.
The thing you said does not exist this is probably similar but most def not what you are looking for
Ah, you mean the protection rules in general.
The thing you said does not exist this is probably similar but most def not what you are looking for
No this is exactly what I mean "Require a pull request before merging". Do this for main please. This should work when you put in main
as naming rule. It can use wildcards, but thats not necessary I think.
This way we can not accidetaly push onto main an break user setups.
I created the rule now.
Please protect the main branch of this repo to prevent accidental pushes to it. (e.g. https://github.com/an-anime-team/aagl-ebuilds/pull/3#issuecomment-1243473424, without the intent to put him to the pillory) In git you can always roll back and change history, but for our users this means additional trouble. Portage can not rebase a repository when syncing it with
emerge --sync
(oremaint
), there is only fast forward. So the users have to delete the files in/var/db/repos/The-Anime-Game
manually and then sync again or do some manual git commands on that repo.For our users updates should go smooth without manual interventions.