-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Pull request merge strategy #712
Labels
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
Milestone
Comments
lunny
added
the
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
label
Jan 21, 2017
It would be so useful to be able to choose a merge strategy. If it helps, this is how GitLab does it, and this is how BitBucket does it. |
+1 on merge strategies, very helpful when I (as a contributor) know I have or will have lots of commits and it should be squashed. |
8 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
A nice feature to have would be squash and rebasing options to accept a pull request, like github does.
I think the UI for the merge options could be something like github, as it's very simple to select a merge option.
Github also has a project configuration UI to enable/disable the pull request merge modes on a per project basis. Not every project mantainers would like to leave all options enabled, so this could be necessary.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: