Github messages for voidlinux
 help / color / mirror / Atom feed
From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] [RFC]: .github: improve the PR template
Date: Tue, 05 Oct 2021 21:17:02 +0200	[thread overview]
Message-ID: <20211005191702.959NexV27z3aJzxc5oZ3ZdJ5PWbXCKi6eDM3LGWmLZo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33118@inbox.vuxu.org>

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

New review comment by Piraty on void-packages repository

https://github.com/void-linux/void-packages/pull/33118#discussion_r722566755

Comment:
not harsh and to the point.

how about something like `*YES*|*NO*` (in bolds) to make it both (even more) obvious to contributor that an answer is required and obvious to maintainer if it wasn't answered (like not checking any checkbox before).

  parent reply	other threads:[~2021-10-05 19:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-25 14:42 [PR PATCH] .github: clarify " paper42
2021-09-25 18:06 ` ericonr
2021-09-25 22:03 ` [PR PATCH] [Updated] " paper42
2021-09-25 22:08 ` [RFC]: .github: improve " paper42
2021-09-27 20:45 ` [PR REVIEW] " Chocimier
2021-09-27 20:45 ` Chocimier
2021-09-28 20:02 ` Piraty
2021-09-29  7:23 ` [PR PATCH] [Updated] " paper42
2021-09-29  7:25 ` [PR REVIEW] " paper42
2021-10-03 21:52 ` [PR PATCH] [Updated] " paper42
2021-10-03 21:56 ` [PR REVIEW] " paper42
2021-10-04 16:04 ` Chocimier
2021-10-05 19:17 ` Piraty [this message]
2021-10-14 16:32 ` Chocimier
2021-10-22 23:06 ` paper42
2021-10-23 10:47 ` Gottox
2021-10-24 17:25 ` [PR PATCH] [Updated] " paper42
2021-10-25 17:42 ` [PR REVIEW] " Chocimier
2021-10-28 22:03 ` paper42
2021-10-29 15:28 ` Chocimier
2021-11-08 22:32 ` Piraty
2021-11-08 23:02 ` Vaelatern
2021-11-09 23:31 ` [PR PATCH] [Merged]: " Piraty

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=20211005191702.959NexV27z3aJzxc5oZ3ZdJ5PWbXCKi6eDM3LGWmLZo@z \
    --to=piraty@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).