Allow repositories to ignore specific injected workflows #50
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Personal/woodpecker-extension#50
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Let a repository opt out of individual workflows injected by the global extension, without changing shared rules or disabling an entire rule.
Motivation
Personal/backstagematches thebun-astrorule and receivesbun-verify,bun-push, andbun-deploy, but it is not an Astro app andbun-deployopens a deployment PR. The label-basedmatch_not_labelsmechanism can exclude a whole rule, but it requires a shared configuration change and cannot keep one workflow from a rule while dropping another. A repository-local list of workflow names is more precise and keeps the decision in the repository.Proposed behavior
Extend the existing root-level
woodpecker.toml:Configuration.name(the[workflows.*]key in the extension configuration).endpoints.routes[].workflowsstay unconditional, matching the current documented behavior.Acceptance criteria
woodpecker.tomlaccepts an optionalignored_workflowslist of strings.Personal/backstagepipeline can dropbun-verify,bun-push, andbun-deploywhile keepingflake-checkandrenovate-lint.Related
Chosen path: implement this feature and release it. Personal/backstage#44 will use
ignored_workflowsto dropbun-verify,bun-push, andbun-deploy; Personal/nixos-configuration#68 is now scoped to bumping and deploying the extension after this ships. The label-basedmatch_not_labelsapproach is dropped.martin referenced this issue from Personal/backstage2026-11-20 19:27:35 +00:00
Backstage no longer plans to use this feature for the
bun-astrofalse positive. The chosen fix is to narrow the shared rule so it requires an Astro config (Personal/nixos-configuration#68). Personal/backstage#44 is closed as superseded. This issue remains a useful general enhancement, but it no longer blocks Personal/backstage#20 or #42.