Scheduled workflows run on contributor forks without repository guards
Maintainers usually reply within 3 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, yaml
- Domain
- ci-cd
Research direction
Read the five named workflow files: ci-weekly.yml, docker-stack-sipnet.yml, docker.yml, integration-test.yml, and download-met-data.yml; compare them with check-links.yml and stale.yml, which already have repository guards. Confirm the workflows skip scheduled runs on forks while remaining eligible to run on PecanProject/pecan.
Written by the indexing model from the issue text.
Description
Bug Description
When contributor forks have GitHub Actions active, scheduled workflows trigger automatically on forks instead of staying restricted to the upstream repository.
When one maintains an active fork of PecanProject/pecan,They expect scheduled jobs to run only upstream. Instead, multiple heavy test and container build workflows trigger on their fork, consuming personal GitHub Actions minutes.
To Reproduce
Steps to reproduce the behavior:
- Fork PecanProject/pecan to a personal GitHub account.
- Ensure GitHub Actions are enabled on the fork.
- Make no commits or code changes.
- Wait for scheduled cron intervals such as Monday 04:30 UTC.
- Observe scheduled workflows executing on the fork.
Expected behavior
Scheduled cron workflows should execute only on the canonical upstream repository (PecanProject/pecan), skipping runs on forks.
Screenshots
N/A
Machine (please complete the following information):
- Server: GitHub Actions (Ubuntu)
- OS: Linux
- Browser: N/A
- Version: develop branch
Additional context
While check-links.yml and stale.yml already include repository guards, five other scheduled workflows lack this check:
ci-weekly.yml(runs Monday 04:30 UTC)docker-stack-sipnet.yml(runs Mon, Wed, Fri 04:30 UTC)docker.yml(runs Monday through Friday 01:30 UTC)integration-test.yml(runs Thursday 04:30 UTC)download-met-data.yml(runs Thursday 04:30 UTC)
Adding a repository check across these five workflows will prevent unwanted fork runs.
- Dominant language
- R
- Stars
- 246
- Forks
- 322
- Avg merge
- 7d 3h
- Merged PRs (30d)
- 17
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PecanProject/pecan
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PecanProject/pecan#4183 · 1 comment ·
Maintainers usually reply within 3 days
-
Tests error instead of skipping when optional packages (ecmwfr, jsonvalidate) or BETY database are unavailablePossibly taken @madhavzanwar claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PecanProject/pecan#4179 ·
Maintainers usually reply within 3 days
-
Add documentation about Docker cleanupMay be free again @soniya-malviy claimed this 625 days ago, and no pull request is open. Opendocumentation Status: Stale
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
PecanProject/pecan#2693 · 2 comments ·
Maintainers usually reply within 3 days
-
do_conversions() silently ignores overwrite.met / overwrite.fia / overwrite.ic for multi-site (MultiSettings) runsPossibly taken @madhavzanwar claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
PecanProject/pecan#4175 ·
Maintainers usually reply within 3 days
-
test_remote() errors on multi-line output instead of reporting the host as working or failingPossibly taken @madhavzanwar claimed this 6 days ago. Open
Difficulty 1/5 1-3 hours Newbie friendliness 25/100
PecanProject/pecan#4168 ·
Maintainers usually reply within 3 days
All issues in PecanProject/pecan
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ropensci-review-tools/pkgstats#136 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Soft restart fails when a dependent domain's parameter is inactivePossibly taken @Saethox claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MLopez-Ibanez/irace#103 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
make sure .Random.seed existsPossibly taken @topepo claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
tidymodels/tune#1211 ·