From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] Enable CI on GitHub Actions
Date: Fri, 06 Nov 2020 01:44:40 +0100 [thread overview]
Message-ID: <20201106004440.rfVE5taXNTpDDrCLD3JSdT7MDv8Gkw64Hzt9rYH_stI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26095@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
New review comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/26095#discussion_r518457076
Comment:
With this `if`, I think the Actions won't build the PR with title or the body (first comment) that has '[ci skip]`, right?
While I like it to not pollute the commit message, I think we should update the README, too.
next prev parent reply other threads:[~2020-11-06 0:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 21:10 [PR PATCH] tmp ericonr
2020-11-02 21:13 ` [PR PATCH] [Updated] tmp ericonr
2020-11-02 21:19 ` ericonr
2020-11-03 14:05 ` ericonr
2020-11-03 19:37 ` [PR PATCH] [Updated] Enable CI on GitHub Actions ericonr
2020-11-03 19:43 ` ericonr
2020-11-03 19:53 ` ericonr
2020-11-03 20:28 ` ericonr
2020-11-03 20:29 ` ericonr
2020-11-03 20:31 ` ericonr
2020-11-03 20:32 ` ericonr
2020-11-03 20:34 ` ericonr
2020-11-03 20:41 ` ericonr
2020-11-03 20:42 ` [PR PATCH] [Updated] Enable CI on GitHub Actions [ci skip] ericonr
2020-11-03 20:46 ` ericonr
2020-11-03 20:53 ` ericonr
2020-11-03 20:56 ` ericonr
2020-11-03 20:58 ` ericonr
2020-11-05 16:27 ` Anachron
2020-11-05 17:22 ` [PR PATCH] [Updated] " ericonr
2020-11-05 17:24 ` [PR PATCH] [Updated] Enable CI on GitHub Actions ericonr
2020-11-05 17:41 ` ericonr
2020-11-05 19:27 ` Anachron
2020-11-05 21:23 ` [PR PATCH] [Updated] " ericonr
2020-11-05 21:24 ` ericonr
2020-11-06 0:41 ` [PR REVIEW] " sgn
2020-11-06 0:41 ` sgn
2020-11-06 0:44 ` sgn [this message]
2020-11-06 1:17 ` ericonr
2020-11-07 23:02 ` ericonr
2020-11-07 23:02 ` ericonr
2020-11-07 23:05 ` [PR PATCH] [Updated] " ericonr
2020-11-07 23:11 ` ericonr
2020-11-07 23:15 ` ericonr
2020-11-08 1:45 ` ericonr
2020-11-08 1:59 ` [PR PATCH] [Updated] " ericonr
2020-11-08 2:01 ` ericonr
2020-11-08 2:09 ` [PR PATCH] [Updated] " ericonr
2020-11-08 2:20 ` ericonr
2020-11-08 2:21 ` ericonr
2020-11-13 22:33 ` [PR PATCH] [Merged]: " ericonr
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=20201106004440.rfVE5taXNTpDDrCLD3JSdT7MDv8Gkw64Hzt9rYH_stI@z \
--to=sgn@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).