M, Jeremy Mitchell <
>> >>> mitchell...@gmail.com
>> >>> > >
>> >>> > > wrote:
>> >>> > >
>> >>> > >> With an issue and/or pr template, we will have 6/6 items checked:
>> >>> > >>
>> >>>
ache/incubator-trafficcontrol/community
> >>> > >>
> >>> > >> I actually think PR templates would be quite helpful. As a
> >>> > >> committer/merger, it would be nice to know what problem the PR is
> >>> > solving
> >>> &
gt; > >>
> >>> > >> I actually think PR templates would be quite helpful. As a
> >>> > >> committer/merger, it would be nice to know what problem the PR is
> >>> > solving
> >>> > >> and how to verify the functionali
> >> tests, documentation, etc.
>>> > >>
>>> > >> I'll take a stab at a couple of templates and run them by the group.
>>> > >>
>>> > >> Jeremy
>>> > >>
>>> > >> On Wed, Jan 31, 2018 at 1:10
gt;
>> > >> On Wed, Jan 31, 2018 at 1:10 PM, Chris Lemmons <alfic...@gmail.com>
>> > wrote:
>> > >>
>> > >>> I'm +1 on Issue Templates, for sure. I don't know that PR templates
>> > >>> are quite as critical, but it might be nic
couple of templates and run them by the group.
>>> >>
>>> >> Jeremy
>>> >>
>>> >> On Wed, Jan 31, 2018 at 1:10 PM, Chris Lemmons <alfic...@gmail.com>
>>> wrote:
>>> >>
>>> >>> I'm +1 on Issue Te
ody, it
>> >>> might be more annoying than valuable, though.
>> >>>
>> >>> I'm also +1 on hiding these particular files in a .github directory.
>> >>> Unlike CONTRIBUTING and README, they don't provide all that much
>> >>> benefit for a new person
>>> overwrites the default comment that you get from the commit body, it
> > >>> might be more annoying than valuable, though.
> > >>>
> > >>> I'm also +1 on hiding these particular files in a .github directory.
> > >>> Unlike
gt; overwrites the default comment that you get from the commit body, it
> > >>> might be more annoying than valuable, though.
> > >>>
> > >>> I'm also +1 on hiding these particular files in a .github directory.
> > >>> Unlike CONTRIBUTI
yan_dur...@comcast.com>
> >>> wrote:
> >>> > Always +1 on standardization and consistency
> >>> >
> >>> > I still want to circle back and setup project/kanbans for organizing
> >>> tickets in Github.
> >>> >
> >
I still want to circle back and setup project/kanbans for organizing
>>> tickets in Github.
>>> >
>>> > Ryan DurfeyM | 303-524-5099
>>> > CDN Support (24x7): 866-405-2993 or cdn_supp...@comcast.com>> cdn_supp...@comcast.com>
>>> >
>>&
omcast.com> cdn_supp...@comcast.com>
>> >
>> > From: Dewayne Richardson <dewr...@gmail.com>
>> > Reply-To: "dev@trafficcontrol.incubator.apache.org" <
>> dev@trafficcontrol.incubator.apache.org>
>> > Date: Wednesday, January 31,
rol.incubator.apache.org>
> > Date: Wednesday, January 31, 2018 at 11:15 AM
> > To: "dev@trafficcontrol.incubator.apache.org" <
> dev@trafficcontrol.incubator.apache.org>
> > Subject: Github PR/Issues Format Templates
> >
> > I was working through th
2018 at 11:15 AM
> To: "dev@trafficcontrol.incubator.apache.org"
> <dev@trafficcontrol.incubator.apache.org>
> Subject: Github PR/Issues Format Templates
>
> I was working through the go-swagger repo and found a bug. I submitted a
> new issue and found this interesting approach I
<dewr...@gmail.com>
Reply-To: "dev@trafficcontrol.incubator.apache.org"
<dev@trafficcontrol.incubator.apache.org>
Date: Wednesday, January 31, 2018 at 11:15 AM
To: "dev@trafficcontrol.incubator.apache.org"
<dev@trafficcontrol.incubator.apache.org>
Subject: Gith
I was working through the go-swagger repo and found a bug. I submitted a
new issue and found this interesting approach I think the TC github should
adopt, "Issue and PR Templates". I think the main value here is
consistency in our PRs/Issues and user friendly prompts to say "these are
the data
16 matches
Mail list logo
