Support semi-linear history (rebase && merge --no-ff) #8940
Replies: 7 comments 15 replies
-
If we require pull requests to be up to date an enable only merge commits we get this behavior, right? |
Beta Was this translation helpful? Give feedback.
-
Yes, please! This would be super useful. Personally more interested in the ability to enforce it and require PRs to be up to date than in a new button to "rebase and merge" in one click. |
Beta Was this translation helpful? Give feedback.
-
This would be a really nice middle ground between 'Squash and merge' and 'Rebase and merge'. IMHO
|
Beta Was this translation helpful? Give feedback.
-
There is a related discussion here, but focused on getting the merge queue to support semi-linear history. |
Beta Was this translation helpful? Give feedback.
-
Azure DevOps has a fantastic UI for this in my opinion, which includes animated visualizations for the different merge strategies. |
Beta Was this translation helpful? Give feedback.
-
If I set these options, perhaps I can update the pull request by rebasing, before I do a normal merge (creating merge commit), right?
|
Beta Was this translation helpful? Give feedback.
-
Sorry if this is not the appropriate place to ask, but am I right that this is still not supported by GitHub? |
Beta Was this translation helpful? Give feedback.
-
Support the concept of semi-linear history as discussed here isaacs/github#1017 (hopefully with an option for enforcement as well).
Example
Beta Was this translation helpful? Give feedback.
All reactions