Commit is not pushable anymore

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Commit is not pushable anymore

SmartGit mailing list
I have a project in SmartGit that is using Git-flow feature branches.
 

 I created a new branch, made the first commit to it, and then pushed it to the server.
 

 However, the commit is still showing up in SmartGit's "Outgoing" window.
 

 When I try to push it again, by right-clicking and choosing "Push Commit", I get the following error:
 Commit [ID] is not pushable anymore.
 

 I checked the Git server and the commit is there.
 

 How can I get that commit out of the "Outgoing" list?
Reply | Threaded
Open this post in threaded view
|

Re: Commit is not pushable anymore

SmartGit mailing list
I, too, have noticed this. I just assumed this was how it worked on branches. The commits do, however, turn light grey once they have been pushed. But, they do stay in the Outgoing window. Our dev and master branches do not have this problem--just branches we've created via Git-flow.
Reply | Threaded
Open this post in threaded view
|

Re: Commit is not pushable anymore

SmartGit mailing list
> I, too, have noticed this. I just assumed this was how it worked on branches. The
> commits do, however, turn light grey once they have been pushed. But, they do stay
> in the Outgoing window. Our dev and master branches do not have this problem--just
> branches we've created via Git-flow.

This is expected: when working on a feature, you may decide to rearrange the commits before finally integrating the feature. This is why you will see all commits of your feature branch.

--
Best regards,
Marc Strapetz
syntevo GmbH
http://www.syntevo.com
http://blog.syntevo.com



08/29/2014 20:30 - [hidden email] [smartgit] wrote:

> I, too, have noticed this. I just assumed this was how it worked on branches. The
> commits do, however, turn light grey once they have been pushed. But, they do stay
> in the Outgoing window. Our dev and master branches do not have this problem--just
> branches we've created via Git-flow.
>