From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: GitHub Action: build on push to non-master branches
Date: Mon, 18 Jan 2021 16:42:20 +0100 [thread overview]
Message-ID: <20210118154220.TygfDcjhn6BQroloAZBgjeg-orxotBSfbx1fbazpbdE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28013@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/28013#issuecomment-762327451
Comment:
I'm concerned about people who aren't aware of this new default getting lots of notifications and spending more CI time than they expect. GH is kinda stupid as well, so it will have separate CI runs for the PR and for the branch in the person's repo.
Anyway, if you think this is useful (and I believe others have requested it as well), we can turn it on. As long as this doesn't impact us too much (by, say, counting the number of machines we are using by including forks), I think we can push as something experimental.
next prev parent reply other threads:[~2021-01-18 15:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 13:52 [PR PATCH] liquid-dsp: fix build sgn
2021-01-18 13:52 ` [PR PATCH] [Closed]: " sgn
2021-01-18 14:02 ` [PR PATCH] [Updated] " sgn
2021-01-18 14:03 ` sgn
2021-01-18 14:20 ` GitHub Action: build on push to non-master branches ericonr
2021-01-18 14:28 ` sgn
2021-01-18 14:30 ` [PR PATCH] [Updated] " sgn
2021-01-18 14:32 ` sgn
2021-01-18 15:42 ` ericonr [this message]
2021-01-19 0:09 ` fosslinux
2021-01-19 0:22 ` sgn
2021-02-25 18:47 ` ericonr
2021-02-25 23:50 ` sgn
2021-02-27 0:32 ` [PR PATCH] [Updated] " sgn
2022-03-27 23:38 ` [PR PATCH] [Merged]: " the-maldridge
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=20210118154220.TygfDcjhn6BQroloAZBgjeg-orxotBSfbx1fbazpbdE@z \
--to=ericonr@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).