Re: How to figure out what 'git push' would do?

From: Julian Phillips <julian@quantumfyre.co.uk>
Date: Aug 5, 2007, 17:45 UTC
Message-ID: <Pine.LNX.4.64.0708051839510.12656@beast.quantumfyre.co.uk>
In-Reply-To: <20070805173340.GA3159@steel.home>

On Sun, 5 Aug 2007, Alex Riesen wrote:

Show 11 quoted lines

> Steffen Prohaska, Sun, Aug 05, 2007 13:37:34 +0200:
>> How can I check what a 'git push' would do, without
>> actually doing it?
>>
>> Is there something like 'git push --dry-run', similar
>> to 'rsync --dry-run'?
>
> No. It is often safe to just do git-push, unless you have naive
> developers doing pull every time some ref in your shared repo changes
> *and* expecting the result to compile (typical for CVS way of work).
> git-push will not overwrite anything, it always only forwards history.

Not strictly true. You _can_ push out non fastforward changes, unless you have receive.denyNonFastforwards in the repote repo - so you may well be able to push out something that is completely unrelated to the last commit the ref pointed to.

-- 
Julian

  ---
You never get a second chance to make a first impression.