Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358100 - Push dialog says [rejected] without giving a clue
Summary: Push dialog says [rejected] without giving a clue
Status: NEW
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 1.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-19 08:17 EDT by Dani Megert CLA
Modified: 2011-10-04 04:40 EDT (History)
1 user (show)

See Also:

Attachments
Picture showing that dialog (11.25 KB, image/png)
2011-09-22 08:08 EDT, Dani Megert CLA 		no flags Details
Screenshot depicting the behaviour in question. (25.79 KB, image/png)
2011-09-23 10:09 EDT, Remy Suen CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2011-09-19 08:17:15 EDT 
1.1.0.201109151100-r.

When I try to push my master branch it says:
    master: master [rejected]
without giving me any clue what's wrong.
Comment 1 Kevin Sawicki CLA 2011-09-19 15:21:26 EDT 
The text area shown below the tree is empty for rejected pushes?
Comment 2 Remy Suen CLA 2011-09-19 18:38:03 EDT 
Sometimes I get a rejected from a fetch about 'initial'.

I think I might've seen this push failure before too, not sure.
Comment 3 Dani Megert CLA 2011-09-20 01:53:53 EDT 
(In reply to comment #1)
> The text area shown below the tree is empty for rejected pushes?

Yes, I'm pretty sure it was.
Comment 4 Kevin Sawicki CLA 2011-09-20 11:28:00 EDT 
That seems odd, did you happen to push from the command line and see different text displayed when it was rejected?
Comment 5 Dani Megert CLA 2011-09-20 12:01:59 EDT 
(In reply to comment #4)
> That seems odd, did you happen to push from the command line and see different
> text displayed when it was rejected?

Unfortunately not. I can do it when I see this next time.
Comment 6 Dani Megert CLA 2011-09-22 08:08:21 EDT 
Created attachment 203835 [details]
Picture showing that dialog
Comment 7 Kevin Sawicki CLA 2011-09-22 11:21:23 EDT 
For that screenshot, were you able to see what the Git command line produced when doing a similar push?
Comment 8 Dani Megert CLA 2011-09-22 11:25:26 EDT 
(In reply to comment #7)
> For that screenshot, were you able to see what the Git command line produced
> when doing a similar push?

Nope, this happened on a test machine where I didn't have Git installed locally.
Comment 9 Remy Suen CLA 2011-09-23 10:09:19 EDT 
Created attachment 203905 [details]
Screenshot depicting the behaviour in question.

(In reply to comment #7)
> For that screenshot, were you able to see what the Git command line produced
> when doing a similar push?

It seems it didn't like my attempt of pushing non-fast-forward updates to the remote repository, Kevin.
Comment 10 Dani Megert CLA 2011-09-26 09:56:50 EDT 
See bug 358893 for reproducible test case but based on 'Fetch from Upstream'.
Comment 11 Kevin Sawicki CLA 2011-09-26 17:44:45 EDT 
The decorator in the tree will now state when a rejection occurs due to non-fast-forward.

http://egit.eclipse.org/w/?p=egit.git;a=commit;h=087e86462f68e535a1a954c3658d139192db65b6
Comment 12 Dani Megert CLA 2011-10-04 04:40:57 EDT 
(In reply to comment #11)
> The decorator in the tree will now state when a rejection occurs due to
> non-fast-forward.
> 
> http://egit.eclipse.org/w/?p=egit.git;a=commit;h=087e86462f68e535a1a954c3658d139192db65b6

I see this now. However, I think the message should improved. What it really wants to say (at least that was the case in the past few days when I encountered that dialog) is that there are changes on the server for the checked out branch and that I first have to pull them. This always solved the problem for me.