Prevent workflows specific to this repo and its management from running on forks #3693
Labels
🤖 aspect: dx
Concerns developers' experience with the codebase
🛠 goal: fix
Bug fix
good first issue
New-contributor friendly
help wanted
Open to participation from the community
🟨 priority: medium
Not blocking but should be addressed soon
🧱 stack: mgmt
Related to repo management and automations
Description
We have a number of workflows for managing the
WordPress/openverse
andWordPress/openverse-infrastructure
repositories that only make sense to run on this repo. These workflows should not run on forks.We can conditionally abort the workflow (by passing it, so that forks are not overrun with workflow failures) by comparing
github.repository
with the allowlisted names of the main/original/upstream repos.Reproduction
This issue was raised by contributor @firatbezir in a discussion #3686.
Additional context
A good way to identify these workflows is to find workflows that run on a schedule. Most management workflows that shouldn't run on forks (like label/meta-files sync and reminders) run on a fixed schedule.
Contributors affected by this issue can completely disable GitHub Actions on their repo. This will not affect their ability to submit PRs as all necessary workflows for a PR to be merged will be run on the upstream repo once a PR is created.
The text was updated successfully, but these errors were encountered: