Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [RFC]: .github: improve the PR template
Date: Sun, 03 Oct 2021 23:52:47 +0200	[thread overview]
Message-ID: <20211003215247.C42goKMOE6BToE4ITbcNg4g2bDzk1c5UiC2sm2Nbk1A@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: 547 bytes --]

There is an updated pull request by paper42 against master on the void-packages repository

https://github.com/paper42/void-packages pr-template-clarify
https://github.com/void-linux/void-packages/pull/33118

[RFC]: .github: improve the PR template
Filling out the "Does it run and build successfully" section is
necessary only when the CI is skipped, but this is easy to miss.
Separate it from the rest of the text to make it clearer.

cc @ailiop-git

A patch file from https://github.com/void-linux/void-packages/pull/33118.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pr-template-clarify-33118.patch --]
[-- Type: text/x-diff, Size: 3164 bytes --]

From 95243404fdf33874305b99b17409b34c174cc57e Mon Sep 17 00:00:00 2001
From: Michal Vasilek <michal@vasilek.cz>
Date: Sat, 25 Sep 2021 14:56:06 +0200
Subject: [PATCH] .github: improve the PR template

* switch from using checkboxes to deleting the lines which are not
  applicable
* make it clear that filling out the part about manual builds is only
  necessary when the CI is skipped, this was easy to miss
---
 .github/pull_request_template.md | 39 ++++++++++++++++----------------
 1 file changed, 19 insertions(+), 20 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 1fdf9e94ea93..5b1ca3b31cb5 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,26 +1,25 @@
-<!-- Mark items with [x] where applicable -->
+<!-- Uncomment relevant sections and delete the lines which are not applicable -->
 
-#### General
-- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
-
-#### Have the results of the proposed changes been tested?
-- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
-- [ ] I generally don't use the affected packages but briefly tested this PR
+<!-- Note: PRs should only have one entry in the following section, otherwise
+it will be assumed they have not been tested at all. -->
+#### Testing the changes
+- I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
+- I generally don't use the affected packages but briefly tested this PR
 
 <!--
-If GitHub CI cannot be used to validate the build result (for example, if the
-build is likely to take several hours), make sure to
-[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
-When skipping CI, uncomment and fill out the following section.
-Note: for builds that are likely to complete in less than 2 hours, it is not
-acceptable to skip CI.
+#### New package
+- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
+-->
+
+<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
+and test at least one native build and, if supported, at least one cross build.
+Ignore this section if this PR is not skipping CI.
 -->
 <!-- 
-#### Does it build and run successfully? 
-(Please choose at least one native build and, if supported, at least one cross build. More are better.)
-- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
-- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
-  - [ ] aarch64-musl
-  - [ ] armv7l
-  - [ ] armv6l-musl
+#### Local build testing
+- I built this PR locally for my native architecture, (ARCH-LIBC)
+- I built this PR locally for these architectures (if supported. mark crossbuilds):
+  - aarch64-musl
+  - armv7l
+  - armv6l-musl
 -->

  parent reply	other threads:[~2021-10-03 21:52 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 ` paper42 [this message]
2021-10-03 21:56 ` paper42
2021-10-04 16:04 ` Chocimier
2021-10-05 19:17 ` Piraty
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=20211003215247.C42goKMOE6BToE4ITbcNg4g2bDzk1c5UiC2sm2Nbk1A@z \
    --to=paper42@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).