From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New Package: mold-1.0.3
Date: Mon, 21 Feb 2022 10:48:48 +0100 [thread overview]
Message-ID: <20220221094848.S0I3WuViB3-H-N188eZFXmQr7loGbSDccQc7Rj6QnVk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35361@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
New comment by kawaiiamber on void-packages repository
https://github.com/void-linux/void-packages/pull/35361#issuecomment-1046670284
Comment:
Yes. You can skip CI while you're working on a package. See [Contributing](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md).
> Continuous Integration
> Pull requests are automatically submitted for Continuous Integration (CI) testing to ensure packages build and pass their tests (on native builds) on various combinations of C library and architecture. Packages that take longer than 120 minutes or need more than 14G of storage to complete their build (for example, Firefox or the Linux kernel) will fail CI and should include [ci skip] in the PR title or body (the comment field when the PR is being opened) to avoid wasting CI builder time.
You can also name PR to `[WIP] New package: mold-1.1` (the p in package is technically supposed to be lowercase) to indicate that the package is still being worked on.
Executive summary:
* put `[ci skip]` in your PR.
* put [WIP] in PR name
next prev parent reply other threads:[~2022-02-21 9:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 20:13 [PR PATCH] " basicfunc
2022-02-02 20:20 ` [PR REVIEW] " kawaiiamber
2022-02-03 7:17 ` [PR PATCH] [Updated] " basicfunc
2022-02-03 7:17 ` [PR REVIEW] " basicfunc
2022-02-21 6:49 ` [PR PATCH] [Updated] " basicfunc
2022-02-21 6:50 ` basicfunc
2022-02-21 6:53 ` basicfunc
2022-02-21 7:00 ` kawaiiamber
2022-02-21 7:00 ` [PR REVIEW] " kawaiiamber
2022-02-21 7:01 ` kawaiiamber
2022-02-21 7:05 ` kawaiiamber
2022-02-21 7:39 ` [PR REVIEW] " basicfunc
2022-02-21 7:39 ` basicfunc
2022-02-21 7:48 ` kawaiiamber
2022-02-21 7:49 ` basicfunc
2022-02-21 7:51 ` basicfunc
2022-02-21 7:52 ` kawaiiamber
2022-02-21 8:04 ` basicfunc
2022-02-21 8:04 ` basicfunc
2022-02-21 8:14 ` kawaiiamber
2022-02-21 8:15 ` kawaiiamber
2022-02-21 9:24 ` [PR REVIEW] " basicfunc
2022-02-21 9:24 ` basicfunc
2022-02-21 9:45 ` [PR REVIEW] " kawaiiamber
2022-02-21 9:46 ` kawaiiamber
2022-02-21 9:48 ` kawaiiamber [this message]
2022-02-21 9:50 ` kawaiiamber
2022-02-21 9:52 ` kawaiiamber
2022-02-21 9:53 ` kawaiiamber
2022-02-21 9:53 ` kawaiiamber
2022-02-21 9:55 ` [PR REVIEW] " kawaiiamber
2022-02-21 9:57 ` kawaiiamber
2022-02-21 9:58 ` kawaiiamber
2022-02-21 10:00 ` kawaiiamber
2022-02-22 17:59 ` [PR REVIEW] " Chocimier
2022-02-22 18:02 ` Chocimier
-- strict thread matches above, loose matches on Subject: below --
2022-01-31 20:04 [PR PATCH] New package: mold-1.0.3 save-buffer
2022-02-02 9:38 ` kawaiiamber
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=20220221094848.S0I3WuViB3-H-N188eZFXmQr7loGbSDccQc7Rj6QnVk@z \
--to=kawaiiamber@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).