From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] CONTRIBUTING.md: add instructions for testing PRs
Date: Wed, 03 Aug 2022 06:10:47 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38447@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
There is a new pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages contrib-testing
https://github.com/void-linux/void-packages/pull/38447
CONTRIBUTING.md: add instructions for testing PRs
I've had to find these instructions time and time again for requesting testing from people, so I figured why not make it part of our documentation. Maybe it will help get more users involved with testing.
Open to suggestions on wording, grammar, missing info, etc.
A patch file from https://github.com/void-linux/void-packages/pull/38447.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-contrib-testing-38447.patch --]
[-- Type: text/x-diff, Size: 1706 bytes --]
From 1222ddc6704bc7faeb809f24e87138c58c8d5151 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Wed, 3 Aug 2022 00:08:14 -0400
Subject: [PATCH] CONTRIBUTING.md: add instructions for testing PRs
---
CONTRIBUTING.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index da3bef29c883..d74dd6203618 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -129,3 +129,24 @@ Please abstain from temporarily closing a pull request while revising the templa
Once the reviewers have merged the pull request, our [build server](http://build.voidlinux.org) is automatically triggered and builds
all packages in the pull request for all supported platforms. Upon completion, the packages are available to all Void Linux users.
+
+## Testing Pull Requests
+
+Testing new package submissions and updates is always helpful, and is a great way to get started with contributing.
+First, [clone the repository](https://github.com/void-linux/void-packages#quick-start) if you haven't done so already.
+Then check out the pull request, either with `github-cli`:
+
+ $ gh pr checkout <number>
+
+Or manually:
+
+ $ git fetch origin pull/<number>/head:<branch-name>
+ $ git checkout <branch-name>
+
+If your local void-packages repository is cloned from your fork, you may need to add the main repository as a remote first:
+
+ $ git remote add upstream https://github.com/void-linux/void-packages.git
+ $ git fetch upstream pull/<number>/head:<branch-name>
+ $ git checkout <branch-name>
+
+Then [build and install](https://github.com/void-linux/void-packages#building-packages) the package and test its functionality.
next reply other threads:[~2022-08-03 4:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 4:10 classabbyamp [this message]
2022-08-03 9:36 ` tranzystorek-io
2022-08-03 9:37 ` tranzystorek-io
2022-08-03 11:00 ` Duncaen
2022-08-03 15:39 ` [PR REVIEW] " Chocimier
2022-08-03 15:39 ` Chocimier
2022-08-03 15:39 ` Chocimier
2022-08-03 16:01 ` [PR PATCH] [Updated] " classabbyamp
2022-08-03 16:02 ` [PR REVIEW] " classabbyamp
2022-08-05 0:34 ` [PR PATCH] [Merged]: " abenson
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38447@inbox.vuxu.org \
--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).