[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: push-access
From: |
David Kastrup |
Subject: |
Re: push-access |
Date: |
Wed, 28 Aug 2013 04:13:04 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
Thomas Morley <address@hidden> writes:
> To revert the unwanted merge I did:
>
> git reset --hard HEAD~20
HEAD~20? Huh.
> To push:
>
> git fetch
> git rebase origin dev/handle-grace
> git push origin HEAD:staging
>
>
> Hope it's ok
Hard to argue with success. As long as you check before pushing, it's
hard to mess up. Git will refuse to push anything that is not direct
progress from the state in the repository, so the worst thing one can
generally do is to push some unintended merge commit or get unwanted
additional commits in.
One thing that's worth doing before pushing is
git commit --amend
and then putting
Issue xxxx:
at the start of the first line in the commit message. That makes it
easier in case of problems to find the respective issue tracker.
--
David Kastrup
- push-access, Thomas Morley, 2013/08/27
- Re: push-access, David Kastrup, 2013/08/27
- Re: push-access, Graham Percival, 2013/08/27
- Re: push-access, Thomas Morley, 2013/08/27
- Re: push-access, Thomas Morley, 2013/08/27
- Re: push-access, David Kastrup, 2013/08/27
- Re: push-access, Thomas Morley, 2013/08/27
- Re: push-access, Thomas Morley, 2013/08/27
- Re: push-access,
David Kastrup <=
- Re: push-access, Graham Percival, 2013/08/27