Block merging if fixup commits exist #210479
Replies: 2 comments
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
I think this would be especially useful for teams that follow a “clean history” workflow. One possible approach would be to add an optional repository or branch protection rule that blocks merging when commits matching Git's fixup conventions are present. It would be helpful if GitHub could also offer an automatic squash or rebase option, with a clear preview of the resulting commit history before merging. This would help teams avoid accidentally merging temporary fixup commits while still allowing maintainers to choose their preferred workflow. Would this work better as an optional branch protection rule, rather than a default behavior for all pull requests? |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
Body
Until Github supports auto-merging fixups, it would be helpful if having fixup commits would automatically block merging until they are squashed.
All reactions