threads / discuss / 9062

I never want to push a given change

Subject: I never want to push a given change

## tl;dr

4 messages between Jul 16, 2007 and Jul 17, 2007.

replies: 3people: 2as markdown or json

nathan bullock· Jul 16, 2007, 16:18 UTC · lore

I have been using git for a little while and one thing that I would like to be able to do is never push a given change, or set of changes.

So lets say I clone a .git repository. Then I make a couple of changes that I don't want anyone else to see, do a commit. Then I make some other changes that I want everyone else to see and do another commit.

How do I push just the second commit? And how do I make it so that every other time I do a push after this that first commit will never be sent?

Thanks, Nathan

ps. I am really enjoying using git. Thanks.

Brian Gernhardt· Jul 17, 2007, 03:12 UTC · re: nathan bullock · lore

Re: I never want to push a given change

On Jul 16, 2007, at 12:18 PM, nathan bullock wrote:

Show 12 quoted lines

> I have been using git for a little while and one thing that I would  
> like to
> be able to do is never push a given change, or set of changes.
>
> So lets say I clone a .git repository. Then I make a couple of changes
> that I don't want anyone else to see, do a commit. Then I make some
> other changes that I want everyone else to see and do another commit.
>
> How do I push just the second commit?
> And how do I make it so that every other time I do a push after  
> this that
> first commit will never be sent?

Generally the way I do such things is multiple branches. Have a branch "local" (or a more descriptive name) that isn't pushed out anywhere. Place any changes you do NOT want shared on that brach. Place changes to be shared on the master or appropriate topic branch. Instead of committing changes to be shared on top of the local ones, use "git rebase" to keep the local branch on top of the shared ones.

~~ B

nathan bullock· Jul 17, 2007, 05:04 UTC · re: Brian Gernhardt · lore

Re: I never want to push a given change

On 7/16/07, Brian Gernhardt <benji@silverinsanity.com> wrote:

Show 24 quoted lines

>
> On Jul 16, 2007, at 12:18 PM, nathan bullock wrote:
>
> > I have been using git for a little while and one thing that I would
> > like to
> > be able to do is never push a given change, or set of changes.
> >
> > So lets say I clone a .git repository. Then I make a couple of changes
> > that I don't want anyone else to see, do a commit. Then I make some
> > other changes that I want everyone else to see and do another commit.
> >
> > How do I push just the second commit?
> > And how do I make it so that every other time I do a push after
> > this that
> > first commit will never be sent?
>
> Generally the way I do such things is multiple branches.  Have a
> branch "local" (or a more descriptive name) that isn't pushed out
> anywhere.  Place any changes you do NOT want shared on that brach.
> Place changes to be shared on the master or appropriate topic
> branch.  Instead of committing changes to be shared on top of the
> local ones, use "git rebase" to keep the local branch on top of the
> shared ones.
>

Ahhh, thanks for that. You forced me to go stare at the git rebase documentation until I actually understood what it does. It looks like that will work perfectly.

Nathan

Brian Gernhardt· Jul 17, 2007, 05:06 UTC · re: nathan bullock · lore

Re: I never want to push a given change

On Jul 17, 2007, at 1:04 AM, nathan bullock wrote:

> Ahhh, thanks for that. You forced me to go stare at the git rebase  
> documentation
> until I actually understood what it does. It looks like that will work
> perfectly.

Well, I was perfectly willing to go into more detail if needed. But sometimes people just need a push in the right direction. Plus, I'm too lazy to go into details until asked. ;-)

Glad I could help. ~~ Brian