From: Animeshz <Animeshz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] .github/workflows: disable scheduled cron jobs on forks
Date: Sun, 29 May 2022 06:28:17 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37339@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
There is a new pull request by Animeshz against master on the void-packages repository
https://github.com/Animeshz/void-packages cron-disable-on-forks
https://github.com/void-linux/void-packages/pull/37339
.github/workflows: disable scheduled cron jobs on forks
#### Testing the changes
- I tested the changes in this PR: **briefly**
Donot runs the cron-jobs of `stale.yml` and `cycles.yml` outside the `void-linux` repository-owner.
A patch file from https://github.com/void-linux/void-packages/pull/37339.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cron-disable-on-forks-37339.patch --]
[-- Type: text/x-diff, Size: 1242 bytes --]
From d00b8308de8d993a63d1c4dc6e32c53d2cc63f44 Mon Sep 17 00:00:00 2001
From: Animesh Sahu <animeshsahu19@yahoo.com>
Date: Sun, 29 May 2022 09:55:39 +0530
Subject: [PATCH] .github/workflows: disable scheduled cron jobs on forks
---
.github/workflows/cycles.yml | 1 +
.github/workflows/stale.yml | 1 +
2 files changed, 2 insertions(+)
diff --git a/.github/workflows/cycles.yml b/.github/workflows/cycles.yml
index 0bd148e77f0a..67045b2ee35f 100644
--- a/.github/workflows/cycles.yml
+++ b/.github/workflows/cycles.yml
@@ -7,6 +7,7 @@ on:
jobs:
cycles:
runs-on: ubuntu-latest
+ if: github.event_name != 'schedule' || (github.event_name == 'schedule' && github.repository_owner == 'void-linux')
container:
image: 'ghcr.io/void-linux/xbps-src-masterdir:20220527RC01-x86_64-musl'
steps:
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
index 160897fedef1..d5f8edd83d88 100644
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -9,6 +9,7 @@ on:
jobs:
stale:
runs-on: ubuntu-latest
+ if: github.event_name != 'schedule' || (github.event_name == 'schedule' && github.repository_owner == 'void-linux')
steps:
- uses: actions/stale@v4
with:
next reply other threads:[~2022-05-29 4:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 4:28 Animeshz [this message]
2022-05-30 20:22 ` dmarto
2022-05-30 20:47 ` dmarto
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37339@inbox.vuxu.org \
--to=animeshz@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).