Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
Date: Wed, 30 Mar 2022 18:56:10 +0200	[thread overview]
Message-ID: <20220330165610.S4Bocs5avYB5Q5g7I54BQa9Is9Jg27KVwH8gjWzZVdI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36411@inbox.vuxu.org>

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

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1083386755

Comment:
> I think it would be nice to have a checkbox for electron applications that would add the electron tag and maybe an option (and a new tag) for proprietary software.

Those could definitely be included as checkboxes, but it's beyond the scope of issue forms to dynamically add tags like that. The new [issue automation](https://docs.github.com/en/issues/trying-out-the-new-projects-experience/automating-projects) can probably do such a thing, but that would require a much larger change (migrating to the new issues/projects entirely). Using a bot that looks for the checkbox/text is another option, which could fit in well with the bot @0x5c has been hacking at that tries to autotag PRs based on changeset contents etc.

> I don't like that we have a lot of static text in the request issue template. The whole "Quality Requirements" section could be replaced with a link to Contributing.md.

Should've been a bit more clear there, the explanatory text does not get included in the final issue, it's just for the person filling out the form to read while the form is being filled.

  parent reply	other threads:[~2022-03-30 16:56 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30  5:34 [PR PATCH] " classabbyamp
2022-03-30  8:37 ` [PR REVIEW] " paper42
2022-03-30  8:37 ` paper42
2022-03-30  8:40 ` paper42
2022-03-30 16:56 ` classabbyamp [this message]
2022-03-30 18:14 ` Chocimier
2022-03-30 23:39 ` [PR REVIEW] " 0x5c
2022-03-31  0:38 ` 0x5c
2022-03-31  1:29 ` 0x5c
2022-04-01 17:49 ` [PR PATCH] [Updated] " classabbyamp
2022-04-01 17:52 ` classabbyamp
2022-04-01 17:53 ` classabbyamp
2022-04-01 17:54 ` classabbyamp
2022-04-01 17:55 ` classabbyamp
2022-04-01 17:58 ` classabbyamp
2022-04-02 21:39 ` [PR PATCH] [Updated] " classabbyamp
2022-04-14 18:44 ` classabbyamp
2022-04-14 18:44 ` classabbyamp
2022-04-14 20:25 ` classabbyamp
2022-04-14 20:38 ` [PR REVIEW] " paper42
2022-04-14 20:38 ` paper42
2022-04-14 20:40 ` classabbyamp
2022-04-14 20:43 ` [PR PATCH] [Updated] " classabbyamp
2022-04-14 20:46 ` [PR REVIEW] " classabbyamp
2022-04-14 20:50 ` 0x5c
2022-04-14 20:57 ` Chocimier
2022-04-14 20:58 ` [PR REVIEW] " 0x5c
2022-04-14 21:13 ` 0x5c
2022-04-14 21:22 ` [PR REVIEW] " paper42
2022-04-14 21:23 ` paper42
2022-04-14 21:23 ` classabbyamp
2022-04-14 21:23 ` classabbyamp
2022-04-14 21:25 ` paper42
2022-04-14 21:29 ` classabbyamp
2022-04-14 21:48 ` [PR PATCH] [Updated] " classabbyamp
2022-04-19 15:33 ` classabbyamp
2022-04-19 17:48 ` Chocimier
2022-04-19 17:59 ` [PR PATCH] [Updated] " classabbyamp
2022-04-19 18:00 ` classabbyamp
2022-04-19 18:00 ` classabbyamp
2022-05-01  6:36 ` [PR REVIEW] " 0x5c
2022-06-10 20:48 ` [PR PATCH] [Updated] " classabbyamp
2022-06-10 20:51 ` classabbyamp
2022-06-10 20:52 ` [PR REVIEW] " classabbyamp
2022-06-10 20:56 ` [PR PATCH] [Updated] " classabbyamp
2022-06-10 20:59 ` classabbyamp
2022-06-14 18:33 ` Chocimier
2022-06-14 19:26 ` [PR PATCH] [Updated] " classabbyamp
2022-06-14 19:27 ` classabbyamp
2022-06-14 19:27 ` classabbyamp
2022-06-14 19:33 ` Chocimier
2022-06-14 19:39 ` [PR PATCH] [Updated] " classabbyamp
2022-06-17  3:44 ` [PR PATCH] [Merged]: " classabbyamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220330165610.S4Bocs5avYB5Q5g7I54BQa9Is9Jg27KVwH8gjWzZVdI@z \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).