On 11/27/2015 05:00 PM, Tomasz Kontusz wrote:
> GitHub should already know about that, is a label useful? It will always be
> at least a bit out of date too.
Yes github knows about this, but I couldn't find a way to access this
information. e.g. filter pull unmergable pull request.
signature.a
GitHub should already know about that, is a label useful? It will always be at
least a bit out of date too.
Dnia 27 listopada 2015 11:56:04 CET, Matthias Beyer
napisał(a):
>On 27-11-2015 11:37:54, Pascal Wittmann wrote:
>> On 11/22/2015 11:06 PM, Nicolas Pierron wrote:
>> > I invite other contr
On 27-11-2015 11:37:54, Pascal Wittmann wrote:
> On 11/22/2015 11:06 PM, Nicolas Pierron wrote:
> > I invite other contributors to join me on this triaging effort, such
> > that this system is not only made for me.
>
> I have just added the label "2.status: merge conflict", to indicate
> which PRs
On 11/22/2015 11:06 PM, Nicolas Pierron wrote:
> I invite other contributors to join me on this triaging effort, such
> that this system is not only made for me.
I have just added the label "2.status: merge conflict", to indicate
which PRs are unmergable.
signature.asc
Description: OpenPGP digi
Thank you Nicolas for all this hard work!
On Sun, Nov 22, 2015 at 11:47 PM, Pascal Wittmann
wrote:
> On 11/22/2015 11:06 PM, Nicolas Pierron wrote:
> > For your information, I modified our list of labels, and kept a few
> > old one as they do not map directly to any label of the new set.
>
> Tha
On 11/22/2015 11:06 PM, Nicolas Pierron wrote:
> For your information, I modified our list of labels, and kept a few
> old one as they do not map directly to any label of the new set.
Thank you, good work!
> I invite other contributors to join me on this triaging effort, such
> that this system i
For your information, I modified our list of labels, and kept a few
old one as they do not map directly to any label of the new set.
Thanks for the link, now I recall reading this on the mailing list, I
think have a target system makes sense, as well as having a
package-class.
On the other hand,
Quoting Vladimír Čunát (2015-11-22 16:16:10)
> For reference, we had a short but closely related discussion about half
> a year ago:
> http://lists.science.uu.nl/pipermail/nix-dev/2015-March/016549.html
>
> Since then the rate of issues and PRs increased a bit, but their
> structure hasn't changed
For reference, we had a short but closely related discussion about half
a year ago:
http://lists.science.uu.nl/pipermail/nix-dev/2015-March/016549.html
Since then the rate of issues and PRs increased a bit, but their
structure hasn't changed significantly, I believe.
Vladimir
smime.p7s
Descri
+1
On Sun, Nov 22, 2015 at 1:41 PM, Rok Garbas wrote:
> +1 on the idea, i would include the whole name of the type of tag, eg:
>
> status: work-in-progress
> status: duplicate
> status: invalid
> status: wontfix
>
> but not holding strong opinion on this. thx for picking this up.
>
>
> --
> Rok
+1 on the idea, i would include the whole name of the type of tag, eg:
status: work-in-progress
status: duplicate
status: invalid
status: wontfix
but not holding strong opinion on this. thx for picking this up.
--
Rok Garbas - http://www.garbas.si
signature.asc
Description: signature
This is a pretty good article about organizing issue tags:
https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/
--
Jascha Geerds
j...@ekby.de
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.
On 21-11-2015 20:16:51, Shea Levy wrote:
> +1 for the general idea.
Same here.
--
Mit freundlichen Grüßen,
Kind regards,
Matthias Beyer
Proudly sent with mutt.
Happily signed with gnupg.
signature.asc
Description: PGP signature
___
nix-dev mailing l
No opinion on the specifics of colors/categories, but +1 for the
general idea.
On 2015-11-21 19:59, Nicolas Pierron wrote:
> Hi everybody,
>
> I spent a day doing triage of newly created bugs and I think the
> labels [1] of our repository are currently a big mess. I think the
> meaning of our la
Hi everybody,
I spent a day doing triage of newly created bugs and I think the
labels [1] of our repository are currently a big mess. I think the
meaning of our labels are not clear for multiple reasons. I will take
a few examples to illustrate my point, and then propose a solution to
fix that.
15 matches
Mail list logo