From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] .github: add pull request template
Date: Sun, 27 Oct 2019 16:52:43 +0100 [thread overview]
Message-ID: <20191027155243.S-Y48G8LCmsd7Yaid54AhO28DsKEmUpF0iYaMubVo0k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15798@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
There is an updated pull request by Piraty against master on the void-packages repository
https://github.com/Piraty/void-packages github-pr-template
https://github.com/void-linux/void-packages/pull/15798
.github: add pull request template
A patch file from https://github.com/void-linux/void-packages/pull/15798.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-github-pr-template-15798.patch --]
[-- Type: text/x-diff, Size: 1537 bytes --]
From 904b4d2a9f98ba2804ce21d2bf00c1c3ad0de1ee Mon Sep 17 00:00:00 2001
From: Piraty <piraty1@inbox.ru>
Date: Sat, 26 Oct 2019 00:56:58 +0200
Subject: [PATCH] .github: add pull request template
---
.github/pull_request_template.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 .github/pull_request_template.md
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 00000000000..0aa6b3d9b56
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,21 @@
+<!-- Please mark items with [x] where applicable -->
+
+<!-- If Travis cannot be used to validate the build result (for example if the
+build exceeds the timecap of 45min), make sure to put "[ci skip]" in the HEAD
+commit, which skips travis builds completely (saves CI resources). Uncomment the
+following section in this case. -->
+<!--
+#### Does it build successfully? (Long builds, > 45min)
+- [ ] I built this PR locally for my native architecture, glibc
+- [ ] I built this PR locally for my native architecture, musl libc
+- [ ] I built this PR locally for at these cross architectures: <!-- check at least two -->
+ - [ ] aarch64
+ - [ ] aarch64-musl
+ - [ ] armv7l
+ - [ ] armv7l-musl
+-->
+
+#### 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
+- [ ] I did not test this PR
next prev parent reply other threads:[~2019-10-27 15:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 23:14 [PR PATCH] " voidlinux-github
2019-10-26 5:06 ` voidlinux-github
2019-10-27 15:52 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-27 15:52 ` voidlinux-github [this message]
2020-11-15 13:41 ` Piraty
2020-12-18 14:14 ` [PR REVIEW] " ahesford
2020-12-18 14:14 ` ahesford
2020-12-18 14:14 ` ahesford
2020-12-18 14:15 ` ericonr
2020-12-18 14:16 ` ericonr
2020-12-18 14:18 ` ericonr
2020-12-21 11:39 ` [PR PATCH] [Updated] " Piraty
2020-12-21 11:39 ` [PR REVIEW] " Piraty
2020-12-21 11:40 ` Piraty
2020-12-21 11:42 ` Piraty
2020-12-21 12:33 ` ericonr
2020-12-21 13:07 ` Piraty
2020-12-21 13:07 ` Piraty
2020-12-21 14:37 ` ericonr
2020-12-21 14:45 ` [PR PATCH] [Updated] " Piraty
2020-12-21 15:03 ` Piraty
2020-12-21 15:03 ` Piraty
2020-12-30 7:29 ` the-maldridge
2021-01-18 12:17 ` [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=20191027155243.S-Y48G8LCmsd7Yaid54AhO28DsKEmUpF0iYaMubVo0k@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).