The answer from INFRA- is that we cannot apply labels since we don’t have write 
access to the repo. Its a side effect of being a git mirror. 

I guess Traffic Server and their shiny Git-Dual setup has some bells and 
whistles we can’t use yet

—Eric

> On Mar 14, 2017, at 9:51 AM, Durfey, Ryan <[email protected]> wrote:
> 
> Starting a wiki page on pull requests guidance to document information like 
> this.
> 
> https://cwiki.apache.org/confluence/display/TC/Github+Pull+Request+Guidance
> 
> Ryan Durfey M | 303-524-5099
> 
> 
> From: "Eric Friedrich (efriedri)" <[email protected]>
> Reply-To: "[email protected]" 
> <[email protected]>
> Date: Monday, March 13, 2017 at 8:09 PM
> To: "[email protected]" 
> <[email protected]>
> Subject: Re: Github "Backport" Label
> 
> I opened an INFRA- JIRA and asked them to create it.
> 
> Why no one can apply labels, I don’t know…
> 
> —Eric
> 
> On Mar 13, 2017, at 10:07 PM, Jeremy Mitchell 
> <[email protected]<mailto:[email protected]>> wrote:
> Actually, I'm a bit surprised you were even able to create the 'backport'
> label - https://github.com/apache/incubator-trafficcontrol/labels
> how did you do that? please tell. :)
> On Mon, Mar 13, 2017 at 7:59 PM, Jeremy Mitchell 
> <[email protected]<mailto:[email protected]>>
> wrote:
> I didn't know we could create labels and apply them. If so, I think this
> would be fantastic...but like Dave, I don't see how to do it. :(
> On Mon, Mar 13, 2017 at 7:57 AM, Phil Sorber 
> <[email protected]<mailto:[email protected]>> wrote:
> You can also search on the branch base. Something like: "is:pr is:open
> base:2.0.x"
> On Mon, Mar 13, 2017 at 7:55 AM Dave Neuman 
> <[email protected]<mailto:[email protected]>> wrote:
> I see the label, but I don't see a way to add the label to existing PRs.
> On Sun, Mar 12, 2017 at 8:38 PM, Eric Friedrich (efriedri) <
> [email protected]<mailto:[email protected]>> wrote:
> I created a new label in Github called “backport”.
> Please tag any PRs with this label to make them easier to find.
> —Eric
> 
> 

Reply via email to