[HTTPS-Everywhere] How should the issue bot label issues?

[sjw at gmx.ch]

Hi

Thanks for bringing this question to the list.

Here are some ideas:
* a 'has patch' label, so bugs with an existing PR can quickly be
reviewed and fixed
* Update 'failing tests' label if all tests are passed successfully.
** Maybe some standard answers for failed tests can automate very basic
review steps.
* labeling 'docs' and 'ruleset-testing' (should be trivial to detect)




Am 11.04.2018 um 04:50 schrieb AJ Jordan via HTTPS-Everywhere:
> Hi all,
>
> Sorry it's taken so long to send this email :-)
>
> As I'm sure many of you know I've been slowly making some improvements
> to the issue format bot I wrote for EFF last summer (see bug
> #14616[1]). One of the things I've written is code to label issues
> based on type, over in PR #14698[2]. However, since I wrote that code,
> the labels that the project uses changed.
>
> I reached out to Sumana to ask what she thought the best course of
> action was, since she and Kate had been working on this kind of
> workflow stuff, and she suggested that I just email the list and
> solicit feedback from the community directly. And here we are!
>
> So, what type of labeling would y'all find most effective? As a
> reminder, the current issue types (which is what this labeling would
> be done based on) are here[3], and we can always add more - though we
> should keep them as simple as possible. (I originally added another
> one until @Hainish pointed out[4] that it was probably adding too much
> complexity.)
>
> Cheers!
>
> AJ
>
>  [1]: https://github.com/EFForg/https-everywhere/issues/14616
>  [2]: https://github.com/EFForg/https-everywhere/pull/14698
>  [3]: https://raw.githubusercontent.com/EFForg/https-everywhere/master/.github/ISSUE_TEMPLATE.md
>  [4]: https://github.com/EFForg/https-everywhere/pull/14698#pullrequestreview-101784413
> _______________________________________________
> HTTPS-Everywhere mailing list
> HTTPS-Everywhere at lists.eff.org
> https://lists.eff.org/mailman/listinfo/https-everywhere


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20180601/a5f262c4/attachment.sig>