Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2241F1047C for ; Thu, 8 Aug 2013 14:04:52 +0000 (UTC) Received: (qmail 95585 invoked by uid 500); 8 Aug 2013 14:04:52 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 95518 invoked by uid 500); 8 Aug 2013 14:04:51 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 94960 invoked by uid 99); 8 Aug 2013 14:04:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Aug 2013 14:04:50 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Aug 2013 14:04:46 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=xDFxF2qp0ZAoJw4a+0YKhYVsyETDqA0CninshyDyX7c=; b=vSl2J2OM56Fw4DamoGpYywi0Z4SFA5NbYFtSEslwDBYLI3ANuzQCWX8vCPyMRYMs4gT5eDFL36d2b4MlNumU7z1xCMa2jOTnSJigg6gC0T6+Yq8oWpRlo2BXTQ0ywnR2U+5ZBBiGjqh6xcLw1MjsjRUUKG3QfMtmlxTTgxexpRw=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-4.v29.ch3.sourceforge.com) by sfs-alluradaemon-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V7QpF-00034c-BW for allura-dev@incubator.apache.org; Thu, 08 Aug 2013 14:04:25 +0000 Content-Type: multipart/related; boundary="===============5180175970235846420==" MIME-Version: 1.0 To: "[allura:tickets] " <5177@tickets.allura.p.re.sf.net> From: "Cory Johns" Reply-To: "[allura:tickets] " <5177@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #5177 Better branch/commit logic when creating new merge requests Message-ID:

Date: Thu, 08 Aug 2013 14:04:25 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============5180175970235846420== Content-Type: multipart/alternative; boundary="===============8220114258721355270==" MIME-Version: 1.0 --===============8220114258721355270== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit - **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 sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============8220114258721355270== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
  • 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 sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============8220114258721355270==-- --===============5180175970235846420==--