Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 387453

Summary:	Changing the default remote to the same in 'more' while pushing causes conflict 409 error
Product:	[ECD] Orion	Reporter:	Maciej Bendkowski <maciej.bendkowski>
Component:	Git	Assignee:	Project Inbox <orion.git-inbox>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	edyta.przymus, maciej.bendkowski, malgorzata.tomczyk, Szymon.Brandys
Version:	unspecified
Target Milestone:	1.0 M2
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Maciej Bendkowski

2012-08-17 03:44:54 EDT

Do some changes in a branch with a defined remote (in my case origin/master). Try to push your changes into the remote. You will be prompted to confirm the remote - click 'More'. From the remote list choose the default remote again. This will cause in an 409 conflict error with the "Config entry for branch.master.remote already exists" message. You will not be prompted for any credentials.

Comment 1 Szymon Brandys

2012-08-17 05:58:27 EDT

Edyta, please take a look.

Comment 2 Edyta Przymus

2012-08-17 06:03:52 EDT

I will fix it ASAP

Comment 3 Edyta Przymus

2012-08-17 07:09:21 EDT

Dear Maciej,

I go through the testcase you described, but the problem didn't occur. The error "Config entry for branch.master.remote already exists" will occur, but it is handled. I am always asked for credentials and the only situation the push doesn't success is when it's non fast-forward, but it is another story.

Comment 4 Maciej Bendkowski

2012-08-17 08:34:48 EDT

(In reply to comment #3)
> Dear Maciej,
> 
> I go through the testcase you described, but the problem didn't occur. The
> error "Config entry for branch.master.remote already exists" will occur, but
> it is handled. I am always asked for credentials and the only situation the
> push doesn't success is when it's non fast-forward, but it is another story.

I humbly apologize. It turns out the real problem is my local repository configuration. I wasn't asked for any credentials, because Orion is unable to modify my git configuration file (404 error). False alarm. I'm closing this bug.