ci: restrict specific workflows to the upstream repository#28778
Open
nimdrak wants to merge 1 commit into
Open
ci: restrict specific workflows to the upstream repository#28778nimdrak wants to merge 1 commit into
nimdrak wants to merge 1 commit into
Conversation
Many GitHub Actions workflows currently trigger on user forks, leading to unnecessary CI resource consumption, unwanted bot behavior, and inevitable failures. This commit restricts these specific workflows to only run on the primary `containers/podman` repository. The restricted workflows fall into two main categories: 1. Require Custom Upstream Secrets: Workflows like `release`, `mac-pkg`, `cherry-pick`, and `dev-bump` rely on secrets (e.g., Apple/Azure certs, PODMANBOT_TOKEN, ACTION_MAIL_*) that are unavailable in forks. 2. Manage Upstream Tracker State: Workflows like `assign`, `stale`, and `labeler` are intended strictly for managing the primary project's issues and PRs. Running them on personal forks creates unwanted noise. Additionally, refactored several complex `if` conditions using YAML multi-line strings (`|`) to maintain and improve readability. Signed-off-by: Byounguk Lee <nimdrak@gmail.com>
nimdrak
force-pushed
the
disable_workflows_in_the_forked
branch
from
35aa661 to
148c2fc
Compare
|
[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore. |
Contributor
Author
|
The failed tests are not related with this PR |
Luap99
requested changes
May 27, 2026
Member
Luap99
left a comment
Luap99
left a comment
There was a problem hiding this comment.
We move the repo soon, lets wait with this until we have the new nmae as we need to change the name again otherwise in a follow up commit.
Contributor
Author
|
@Luap99 Got it, thanks for letting me know! |
Member
|
The new repo location will be |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixed #28757
All GitHub workflows fail because they require secrets. The only exception is
zizmor.yaml, which runs a static analysis security check on GitHub Actions.Here is the corrected list of workflows that should be restricted to upstream(
containers/podman), categorized by why they will fail or act improperly in a fork:They rely on secrets that are only available in the upstream repository:
check_cirrus_cron.yml: UsesACTION_MAIL_*secrets for alerting.cherry-pick.yml: UsesCHERRY_PICK_TOKENto automate pushing to release branches.dev-bump.yml: UsesPODMANBOT_TOKENto push version bumps.first_contrib_cert_generator.yml: UsesCERTIFICATES_REPO_TOKENto commit to the external contributor certificates repo.issue_pr_lock.yml: UsesSTALE_LOCKING_APP_PRIVATE_KEYandACTION_MAIL_*secrets.machine-os-pr.yml: UsesPODMANBOT_TOKENto push updates.release.yml: The primary release pipeline; requires Apple signing (MACOS_*), Azure signing (AZ_*),ACTION_MAIL_*, andPODMANBOT_TOKEN.update-podmanio.yml: UsesPODMANBOT_TOKENto push updates to thecontainers/podman.iorepository.These workflows require write permissions to automatically manage issues, labels, and assignments.
assign.yml: Self-assigns issues.issue-labeler.yml: Automatically applies labels to new issues.labeler.yml: Automatically applies labels to PRs based on changed file paths.needs-info-labeler.yaml: Automates comments when theneeds-infolabel is added.stale.yml: Marks older issues and PRs as stale and closes them.➕ Additional Details
I refactored several complex
ifconditions using YAML multi-line strings (|) to improve readability and maintainability.Does this PR introduce a user-facing change?