GitLab

Created by: qfox

How to reproduce:

• Push something to a branch test
• Create MR for branch test
• git push origin :test
• git push origin test
• Open MR again

After rebasing branch, we removing it and pushing again. It makes existing MR empty. It still contains old commits but Changes tab shows 0 changes.

How to force gitlab to refresh branch? Probably branch removes should trigger branch cache drop or something else?

Version 7.1 community

Created by: jchristi

👍 I'm using 6.5, and the behavior I see is a little different though ultimately the same (all the previous changes still show, but no new changes show). The work around is to edit the MR and click save (don't have to actually edit anything). It would be great if I did not have to do this step though.

By Administrator on 2014-09-09T11:36:58 (imported from GitLab project)

Created by: qfox

@jchristi Yes, in previous version it was a little bit better. ;-) But not now. ;-(

And now there is no branch selector in edit form. So I can't change it twice to force refreshing MR.

By Administrator on 2014-09-09T11:39:55 (imported from GitLab project)