Github messages for voidlinux
 help / color / mirror / Atom feed
From: Animeshz <>
Subject: Re: .github/workflows: disable scheduled cron jobs on forks
Date: Tue, 31 May 2022 05:19:20 +0200	[thread overview]
Message-ID: <20220531031920.w8JwpJ_lCgSmR7IAExGGYbmyZlB6sx1bw6YxjFy2rZA@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

New comment by Animeshz 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 mean you have a manual workflow dispatch trigger which should 'just work' in case you want it to... I just prefer not to run the scheduled cron jobs on all the possible forks which may not expect it to run.

> I for one, want to keep the cycle action in my fork, as I do use my master branch for personal packages.

Its also better to have a [seperate repository]( for personal packages (not yet reviewed, or some not even acceptable - e.g. packages that don't tag them as versions), because seperate repository will give a proper overview what packages have been added, and you can easily track their updates if you want to, and add custom actions.

> most existing forks will probably never get this change;

Probably right but change for good always have a positive impact overall

  parent reply	other threads:[~2022-05-31  3:19 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
2022-05-31  3:19 ` Animeshz [this message]
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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220531031920.w8JwpJ_lCgSmR7IAExGGYbmyZlB6sx1bw6YxjFy2rZA@z \ \ \

* 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).