开发者

git: push a single commit

开发者 https://www.devze.com 2022-12-12 03:28 出处:网络
Say I made several commits and wish to cherry pick which ones I push to the remote repositor开发者_StackOverflow社区y. How can I do that (in ascii: C1->C2->C3->C4 and I want to push C2 and C4). Will r

Say I made several commits and wish to cherry pick which ones I push to the remote repositor开发者_StackOverflow社区y. How can I do that (in ascii: C1->C2->C3->C4 and I want to push C2 and C4). Will reordering with rebase, resetting, pushing and then resetting work? (C1->C2->C3->C4 => C2->C4->C1->C3 => reset C4 => push => reset C3). Is there a nicer way?


You may be looking for:

git push origin $commit:$branch

Credit: http://blog.dennisrobinson.name/push-only-one-commit-with-git/

Explanatory notes:

  • Pushing a commit pushes all commits before it (as Amber said). The key is to reorder your commits first (git rebase -i), so they are in the order you want to push them.
  • $commit doesn't have to be a sha1. For example, "HEAD~N" would push everything before the last N commits.
  • $branch (typically "master" or "main") is the branch you push to – the remote branch. It does not have to be the same as a local branch.
  • If you need to get some commits out of the way locally, you can use the cherry-pick method (suggested by midtiby) to move them onto a separate local branch first. But as shown here, it's not necessary to create a local branch for the purpose of pushing to a remote branch. You can work on multiple branches at once if you are careful about which commits you push where.

If the remote branch does not exist yet, and you want to create it, it must be prefixed with refs/heads/ (to disambiguate branch from tag):

git push origin $commit:refs/heads/$branch

And as a variation of this theme, deleting a remote branch can be thought of as pushing no commit to it:

git push origin :$branch

Pro tip: git-revise is a tool for massaging your commit stack into shape before pushing. It has a similar interface to git rebase. This tool is irreplaceable (correct me if I'm wrong) for sufficiently hard commit untangling jobs, though its interface is in dire need of replacement.


If you have your commits on a private branch, you can cherry pick commits from the private branch and apply them to the official branch. At this point you can now push all your commits on the official branch (which is the subset that you previously cherry picked).


$ git push <remote name> <commit hash>:<remote branch name>

# Example:
$ git push origin 2dc2b7e393e6b712ef103eaac81050b9693395a4:master


IIRC, due to how git considers commits to work, C4 inherently includes C3, so the concept of "pushing C4 but not C3" doesn't make sense to git (and likewise C2 relative to C1). (See the answer to this previous question.)

0

精彩评论

暂无评论...
验证码 换一张
取 消