Re: wishlist: make it possible to amend commit messages after push to remote

From: Philip Oakley <philipoakley@iee.org>
Date: Aug 7, 2015, 21:02 UTC
Message-ID: <43BA4A09C14A43DEB23F4F14C2279A30@PhilipOakley>
In-Reply-To: <55C4E77C.8070402@iki.fi>

From: "Jarkko Hietaniemi" <jhi@iki.fi>

Show 11 quoted lines

> Thanks (also to Jacob Keller), the git-notes might work in some cases.
> But it's obviously a pasted-on solution, requiring a different usage,
> e.g. "git log --notes", and whatever other UIs do with it.
>
>> One more thing, if you know that no one has fetched the branch you 
>> just
>> pushed yet, you can amend the commit and force-push it without any
>> problems (I'd sugget using --force-with-lease).
>
> In my particular case, not going to work, multiple CI engines jump
> hungry at every commit.

Sound like you need an intermediate repo (similar in style to a personal github repo) between your personal machine and the CIs so that you get the chance to do those rebases/amendments, before you finally push to the CI.

It's almost the same human psychology issue as realizing what to do _after_ sending an email asking for help (and wanting to recall the email...).

To me, part of the sucess of a DVCS is having that extra layer where control has been distributed to you, rather than control still being with 'them'.

</bikeshedding> -- Philip