-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Enforce that PRs are not opened from the 'master' branch of a fork #6899
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Preview available at https://egui-pr-preview.github.io/pr/6899-emilkenforce-no-prs-from-master |
Just want to comment, that it should be possible to push to master branch of other repository, see for example tafia/quick-xml#857, where I made a force-push to master branch of a contributor. |
I believe it is possible if the user has not protected their master branch (which they probably should). And force-pushing to someone else |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I guess we have to merge this to see if this works
Tested sucessfully in |
### Related * Based on emilk/egui#6899 * Tested successfully in emilk/egui#7028 ## What Fail all PRs that are opened from the `main` branch of the fork. ## Why PR:s opened from the `main` branch cannot be collaborated on. That is, we maintainers cannot push our own commits to it (e.g. to fix smaller problems with it before merging). This is because `main` is usually protected (and even if it isn't, it probably _should_ be, and we should not push commits directly into the `main` of some fork)
What
Fail all PRs that are opened from the master/main branch of the fork.
Why
PR:s opened from the
master
branch cannot be collaborated on. That is, we maintainers cannot push our own commits to it (e.g. to fix smaller problems with it before merging).How
Untested code straight from Claude 3.7 😅