Bugzilla – Full Text Bug Listing
| Summary: | Push dialog says [rejected] without giving a clue | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Dani Megert <daniel_megert> | ||||||
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> | ||||||
| Status: | NEW --- | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | remy.suen | ||||||
| Version: | 1.1 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
The text area shown below the tree is empty for rejected pushes? Sometimes I get a rejected from a fetch about 'initial'. I think I might've seen this push failure before too, not sure. (In reply to comment #1) > The text area shown below the tree is empty for rejected pushes? Yes, I'm pretty sure it was. That seems odd, did you happen to push from the command line and see different text displayed when it was rejected? (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. Created attachment 203835 [details]
Picture showing that dialog
For that screenshot, were you able to see what the Git command line produced when doing a similar push? (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. 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. See bug 358893 for reproducible test case but based on 'Fetch from Upstream'. 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 (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. |
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.