incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cory Johns" <>
Subject [allura:tickets] #5177 Better branch/commit logic when creating new merge requests
Date Thu, 08 Aug 2013 14:04:25 GMT
- **labels**: merge-requests, 42cc --> merge-requests
- **status**: open --> code-review
- **assigned_to**: Cory Johns
- **Milestone**: forge-backlog --> forge-aug-09


** [tickets:#5177] Better branch/commit logic when creating new merge requests**

**Status:** code-review
**Labels:** merge-requests 
**Created:** Mon Oct 22, 2012 08:44 PM UTC by Dave Brondsema
**Last Updated:** Wed Aug 07, 2013 09:29 PM UTC
**Owner:** Cory Johns

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.


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message