#5177 Better branch/commit logic when creating new merge requests
closed
General
2015-08-20
2012-10-22
No
It's easy to create merge requests with the wrong branches & commits specified. It defaults both branch drop-downs to the first one alphabetically. It should default to master for git and default? for hg. Potentially look at the branches to see which one(s) have new commits, to be even smarter about the default options. There should be a warning or error if 0 commits are included in the request.
Wayne also suggested having the local branch default to the one you were just looking at.
Can use
app.default_branch_namefor the destination.We shouldn't have to do any fancy stuff like looking to see which branches have new commits.
allura:cj/5177Works well, but I'd be happier to see a test case, or enhancement to existing
test_merge_request_*tests (e.g. something simple like following the link on the sidebar and check that the selected branch is correct)Force-pushed test case:
allura:cj/5177