From: dmarto <email@example.com>
Subject: Re: .github/workflows: disable scheduled cron jobs on forks
Date: Mon, 30 May 2022 22:47:07 +0200 [thread overview]
Message-ID: <20220530204707.hE9YXpIZYKaTpXPkvFVvYi_Iu0jl42BEqERFB4c0HOE@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
New comment by dmarto on void-packages repository
You can stop *all* actions from the settings of your fork (if you don't want them), while if you want to keep them, you will have to maintain a commit that undoes that. I for one, want to keep the cycle action in my fork, as I do use my master branch for personal packages.
And in general, I am not a fan of embedding such "code actions" i.e the code shouldn't care in which repo it is or who is the owner of the repo. At least in my mind, when I fork something I expect 1:1. (off-topic, I bet some may will find it fun to use an action that deletes commit if inside forks - DRM by GithubAction (trademark pending))
Anyway, if the larger consensus is that this is better, I won't be mad or sad; I will simply revert it for myself.
if: github.repository_owner == 'void-linux' || github.event_name != 'schedule'
is a more clear version (disclaimer, not tested).
For the `stale` workflow, it does make sense to have it disabled; and there for sure isn't any use inside forks.
On another note, most existing forks will probably never get this change; as most people fork and rarely update (and push) master, so if the reason is saving resources for GitHub, it is not a good reason.
next prev parent reply other threads:[~2022-05-30 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 4:28 [PR PATCH] " Animeshz
2022-05-30 20:22 ` dmarto
2022-05-30 20:47 ` dmarto [this message]
2022-05-31 3:19 ` Animeshz
2022-05-31 3:27 ` classabbyamp
2022-05-31 3:34 ` Animeshz
2022-05-31 4:00 ` 0x5c
2022-08-30 2:14 ` github-actions
2022-09-13 2:15 ` [PR PATCH] [Closed]: " github-actions
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).