From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: .github: add notice to delete the [ci skip] block
Date: Mon, 18 Jan 2021 14:26:09 +0100 [thread overview]
Message-ID: <20210118132609.CiTgfvP_to0keRj95bRByZPyOwtT654xldvGIUvrI3Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28010@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/28010#issuecomment-762249597
Comment:
Maybe we should include CI skip directions in the manual or some readme file and link to it here rather than including the literal `[ci skip]` here and relying on people to remove it.
Something like, in Markdown link syntax, "... make sure to [skip CI] (some/doc/URL)".
next prev parent reply other threads:[~2021-01-18 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 13:02 [PR PATCH] " Piraty
2021-01-18 13:03 ` [PR PATCH] [Updated] " Piraty
2021-01-18 13:26 ` ahesford [this message]
2021-01-18 13:43 ` Piraty
2021-01-18 14:01 ` [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=20210118132609.CiTgfvP_to0keRj95bRByZPyOwtT654xldvGIUvrI3Y@z \
--to=ahesford@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).