ChatGPT解决这个技术问题 Extra ChatGPT

How can I merge multiple commits onto another branch as a single squashed commit?

I have a remote Git server, here is the scenario which I want to perform:

For each bug/feature I create a different Git branch

I keep on committing my code in that Git branch with un-official Git messages

In top repository we have to do one commit for one bug with official Git message

So how can I merge my branch to remote branch so that they get just one commit for all my check-ins (I even want to provide commit message for this)?

Do you want to keep the individual commits on those other branches?
I typically use git rebase -i to collapse all my commits into one commit and re-write the commit message. Then I send it upstream.
git merge --squash does it all on the command line in one shot and you just hope it works. git rebase -i brings up an editor and lets you fine-tune the rebase. It's slower, but you can see what you're doing. Also, there are difference between rebase and merge which are a little too involved to address in a comment.
the problem with all these answers is that you have to be on the master branch locally and the run the merge --squash command... I want to run the merge --squash from the feature branch not the master branch..so that when I am done, I can push the feature branch to the remote and submit a PR, is that possible?
@AlexanderMills, I think you just need a second feature branch (cloned from the master branch). Do the merge --squash from the old to the new one, and then merge the new branch to master. The old branch becomes obsolete.

a
am0wa

Say your bug fix branch is called bugfix and you want to merge it into master:

git checkout master
git merge --squash bugfix
git commit

This will take all the commits from the bugfix branch, squash them into 1 commit, and merge it with your master branch.

Explanation:

git checkout master

Switches to your master branch.

git merge --squash bugfix

Takes all commits from the bugfix branch and groups it for a 1 commit with your current branch.
(no merge commit appears; you could resolve conflicts manually before following commit)

git commit

Creates a single commit from the merged changes.

Omitting the -m parameter lets you modify a draft commit message containing every message from your squashed commits before finalizing your commit.


If you want to keep references to the old commit messages you can write git commit (without -m param) and you will get to modify a drafted commit message containing all commit messages that you squashed.
You can achieve the same by doing git commit --amend -m '...' later on.
In case merge conflicts happen and you resolve these conflicts, git commit will no longer show the useful commit message containing all commit messages you squashed. In that case, try git commit --file .git/SQUASH_MSG (via stackoverflow.com/a/11230783/923560 ).
Keep in mind that squashing will by default attribute the commits to the squasher. To keep the original author, you need to explicitly specify it like so: git commit -a --author="Author" --message="Issue title #id"
git merge --squash allows you to create a single commit on top of the current branch whose effect is the same as merging another branch. But it won't produce the merge record, which means your pull-request as result would have no changes, yet won't be marked as merged! So, you will need just to delete that branch to be done.
D
Dan Kohn

What finally cleared this up for me was a comment showing that:

git checkout main
git merge --squash feature

is the equivalent of doing:

git checkout feature
git diff main > feature.patch
git checkout main
patch -p1 < feature.patch
git add .

When I want to merge a feature branch with 105(!!) commits and have them all squashed into one, I don't want to git rebase -i origin/master because I need to separately resolve merge conflicts for each of the intermediate commits (or at least the ones which git can't figure out itself). Using git merge --squash gets me the result I want, of a single commit for merging an entire feature branch. And, I only need to do at most one manual conflict resolution.


I highly suggest performing the merge in the feature branch first git merge master, and only then git merge --squash feature in the master branch.
@dotancohen Sorry to dredge up an old comment :) What is gained from merging in the feature branch before performing git merge --squash feature from the master branch?
You want to merge master into the feature branch first, and deal with any manual fixes in your feature branch. That also lets you run tests and make sure your feature branch works correctly. Then, you are guaranteed that you can do an automatic merge of your feature branch into master.
@dankohn I suggest you add the explanation in your above comment into your answer.
@bitsmack: you would merge master into feature first. This give you the opportunity to resolve conflicts on the feature before merging the feature into master
R
Rod

You want to merge with the squash option. That's if you want to do it one branch at a time.

git merge --squash feature1

If you want to merge all the branches at the same time as single commits, then first rebase interactively and squash each feature then octopus merge:

git checkout feature1
git rebase -i master

Squash into one commit then repeat for the other features.

git checkout master
git merge feature1 feature2 feature3 ...

That last merge is an "octopus merge" because it's merging a lot of branches at once.

Hope this helps


Why are you rebasing?
@UmairAshraf it's an interactive rebase which gives you the option to do a squash within your branch.
Rebasing is a bad idea. Don't rebase already published commits
@Sebi2020 git merge --squash will rebase your already published commits in a way that's worse than an interactive rebase. An interactive rebase (on a feature branch) carry little to no adverse effects.
@xiix This only holds true if you the only one working with the feature branch. This is not an assumption you can make. I recommend to read the pages related to rebasing on Git-SCM. It states "Do not rebase commits that exist outside your repository and people may have based work on them." And if you don't know for sure if people already based work on published commits (which you can't know because of the decentral nature of git) you shouln't do that.
V
Vagelis Prokopiou

Merge newFeature branch into master with a custom commit:

git merge --squash newFeature && git commit -m 'Your custom commit message';

If instead, you do

git merge --squash newFeature && git commit

you will get a commit message that will include all the newFeature branch commits, which you can customize.

I explain it thoroughly here: https://youtu.be/FQNAIacelT4


s
spottedmahn

Suppose you worked in feature/task1 with multiple commits.

Go to your project branch (project/my_project) git checkout project/my_project Create a new branch (feature/task1_bugfix) git checkout -b feature/task1_bugfix Merge with the --squash option git merge --squash feature/task1 Create a single commit git commit -am "add single comments" Push your branch git push --set-upstream origin feature/task1_bugfix


q
qwertzguy

If you have already git merge bugfix on main, you can squash your merge commit into one with:

git reset --soft HEAD^1
git commit

git reset --soft HEAD^1 seems to undo the last commit performed before the merge, at least in case of the merge being a fast-forward.
@JesperMatthiesen in case of a fast-forward you don't get a merge commit, so then you would do git reset --soft HEAD^<number-of-commits-to-squash>.
This helped me to squash everything into a single commit after a downstream merge.
A
Aaron

I know this question isn't about Github specifically, but since Github is so widely used and this is the answer I was looking for, I'll share it here.

Github has the ability to perform squash merges, depending on the merge options enabled for the repository.

If squash merges are enabled, the "Squash and merge" option should appear in the dropdown under the "Merge" button.

https://i.stack.imgur.com/gxz2l.png


GitHub uses the default email associated with your account. If you have multiple email addresses, and you need to use a secondary one, you can't use GH UI.
very relevant! Thanks!
J
Jool

To squash your local branch before pushing it:

checkout the branch in question to work on if it is not already checked out. Find the sha of the oldest commit you wish to keep. Create/checkout a new branch (tmp1) from that commit. git checkout -b tmp1 Merge the original branch into the new one squashing. git merge --squash Commit the changes which have been created by the merge, with a summary commit message. git commit -m Checkout the original branch you want to squash. git checkout Reset to the original commit sha you wish to keep. git reset --soft Rebase this branch based on the new tmp1 branch. git rebase tmp1 That's it - now delete the temporary tmp1 branch once you're sure everything is ok.


D
Demian Berisford-Maynard

For Git

Create a new feature

via Terminal/Shell:

git checkout origin/feature/<featurename>
git merge --squash origin/feature/<featurename>

This doesnt commit it, allows you to review it first.

Then commit, and finish feature from this new branch, and delete/ignore the old one (the one you did dev on).


@Melebius The only reference to "SourceTree" is in your sentence, if it was a tag or previous question: It doesn't exist anymore.
@JordanStefanelli SourceTree was used in the original version of this answer. Thanks for notifying it’s fixed!
i
izy
git checkout YOUR_RELEASE_BRANCH
git pull
git checkout -b A_NEW_BRANCH
git merge --squash YOUR_BRANCH_WITH_MULTIPLE_COMMITS
git commit -am "squashing all commits into one"
git push --set-upstream origin A_NEW_BRANCH

Thank you for including the pull. All the other responses seem to assume that nothing has changed in the remote release branch since the last time you were hanging out on it....
R
ResUta

if you get error: Committing is not possible because you have unmerged files.

git checkout master
git merge --squash bugfix
git add .
git commit -m "Message"

fixed all the Conflict files

git add . 

you could also use

git add [filename]

B
Breton F.

Your feature branch is done and ready to commit to master, develop or other target branch with only one commit

Go to merge branch : git checkout master && git pull

Create a work branch from your clean local master : git checkout -b work

Merge squash your feature branch on work : git merge --squash your_feature_branch.

Commit with default or a new message : git commit (with a specific or default message)

Go back to your feature branch : git checkout your_feature_branch

Point your feature branch to work dir : git reset --hard work

Verify but you are ready to push : git push -f

Then clean up work branch if needed

Replace master with your target branch : develop and so on

No need to specify how many commit from your master to your feature branch. Git takes care*


P
Pavan kumar D

Assume the name of the branch where you made multiple commits is called bugfix/123, and you want to squash these commits. First, create a new branch from develop (or whatever the name of your repo is). Assume the name of the new branch is called bugfix/123_up. Checkout this branch in git bash -

git fetch

git checkout bugfix/123_up

git merge bugfix/123 --squash

git commit -m "your message"

git push origin bugfix/123_up

Now this branch will have only one commit with all your changes in it.


s
sheerun

You can use tool I've created to make this process easier: git-squash. For example to squash all commits on feature branch that has been branched from master branch, write:

git squash master
git push --force

G
Gino Mempin

Use

git status 

to check what's going on.

Then

git checkout master 
git merge --squash bugfix
git add (add which files you want or use wildcard command like ".")

Then

git commit -m "message"

And now last but not the least

git push -u origin master

Here origin can be other remote you prefer.