Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] [RFC] Add a label `needs-testing` for PRs that have not been tested and unconfirmed issues
@ 2022-06-08 14:46 paper42
  2022-06-10 20:22 ` paper42
  2022-06-10 20:22 ` [ISSUE] [CLOSED] " paper42
  0 siblings, 2 replies; 3+ messages in thread
From: paper42 @ 2022-06-08 14:46 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

New issue by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/37448

Description:
Sometimes people (mostly upstream developers that are not using Void) open a PR they didn't test. I mark them with the `help-wanted` label and add a comment explaining that testing has to be done because just adding the `help-wanted` label would be confusing. I propose adding a new label `testing-needed` for this purpose. This should also be used for PRs that have been tested by the author, but need more testing (openssh, mesa, etc.).

This label would also be added automatically to new bug issues (along with the `bug` label) and removed manually when someone reproduces the bug. Confirmed bugs (without the `testing-needed` label) would be excluded from closing with the stale bot.
https://github.com/void-linux/void-packages/pull/36411#discussion_r850787479

I will give this issue a few days and then create the label if there are no comments.

cc @classabbyamp @0x5c

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ISSUE] [CLOSED] [RFC] Add a label `needs-testing` for PRs that have not been tested and unconfirmed issues
  2022-06-08 14:46 [ISSUE] [RFC] Add a label `needs-testing` for PRs that have not been tested and unconfirmed issues paper42
  2022-06-10 20:22 ` paper42
@ 2022-06-10 20:22 ` paper42
  1 sibling, 0 replies; 3+ messages in thread
From: paper42 @ 2022-06-10 20:22 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]

Closed issue by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/37448

Description:
Sometimes people (mostly upstream developers that are not using Void) open a PR they didn't test. I mark them with the `help-wanted` label and add a comment explaining that testing has to be done because just adding the `help-wanted` label would be confusing. I propose adding a new label `testing-needed` for this purpose. This should also be used for PRs that have been tested by the author, but need more testing (openssh, mesa, etc.).

This label would also be added automatically to new bug issues (along with the `bug` label) and removed manually when someone reproduces the bug. Confirmed bugs (without the `testing-needed` label) would be excluded from closing with the stale bot.
https://github.com/void-linux/void-packages/pull/36411#discussion_r850787479

I will give this issue a few days and then create the label if there are no comments.

cc @classabbyamp @0x5c

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC] Add a label `needs-testing` for PRs that have not been tested and unconfirmed issues
  2022-06-08 14:46 [ISSUE] [RFC] Add a label `needs-testing` for PRs that have not been tested and unconfirmed issues paper42
@ 2022-06-10 20:22 ` paper42
  2022-06-10 20:22 ` [ISSUE] [CLOSED] " paper42
  1 sibling, 0 replies; 3+ messages in thread
From: paper42 @ 2022-06-10 20:22 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 157 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/37448#issuecomment-1152710124

Comment:
label created

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-06-10 20:22 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-08 14:46 [ISSUE] [RFC] Add a label `needs-testing` for PRs that have not been tested and unconfirmed issues paper42
2022-06-10 20:22 ` paper42
2022-06-10 20:22 ` [ISSUE] [CLOSED] " paper42

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).