Closed NyaMisty closed 1 year ago
@elsiehupp
Also I strongly advice you to give other member more permission. Currently there's several problems:
If you do concern the repo security you can do the backup regularly instead :).
You didn't enable rebase merge, which is a very very bad idea for big multi-commit PR I'm always posting
I did this because when I have done pull requests with Nextcloud, they always say to squash before merging, and if there are too many changes for this to be reasonable, to do multiple pull requests.
That said, I re-enabled all the various types of merges, since I don't have that strong a preference, either way, and reviewers can make recommendations as they see fit.
I also just changed the default member permissions to "write". The only other person I'd be comfortable giving full admin access at this point is Federico, and in that case the thing to do would be transferring repositories to his existing organization.
Regarding protecting the master branch... if you have a specific recommendation of how I could do mandatory pull request reviews without doing so, let me know, but other than that I would say that's what other branches are for?
By the way, regarding tagging me: right now I get a firehose of email from this repository, and I'm not sure how to dial it down, so if you want to get ahold of me specifically, the best way is to email me using the email on the "Collaborators" pinned discussion.
Do not use squash merge, that forces Git to combine several commit into a huge one, very bad.