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
Change merge guidelines (external contributors can't merge themselves) - also probably move this to a new contributing.md (see Add CONTRIBUTING.md #424 )
Things that can only be done after switching to public:
Add branch protection rules:
Disable (force) push to main
Require at least one approving review/no review requesting changes before merging
Require all checks to pass before merging
Require all conversations to be resolved before merging
(Maybe) Use "Require linear history" feature
(Maybe) Use "Require merge queue" feature - It seems like this will always use fast-forward instead of squash
The text was updated successfully, but these errors were encountered:
We don't really need that if we use github hosted runner, right? So we should just remove access to our self-hosted runner for the entire repo (or just completely remove the runner form our server - right now kampi dot en ge is the only repo using it.)
External contributors can never merge their own PRs. There is not even a setting that would allow that.
Yes, but the guidelines say that they should merge themselves ;)
The current plan is to make this repo public once the "Proof of Concept v0.1.0" milestone is finished.
Here is a (probably incomplete) list of thing to before switching to public:
contributing.md
(see Add CONTRIBUTING.md #424 )Things that can only be done after switching to public:
The text was updated successfully, but these errors were encountered: