ci: add application quality gates to Woodpecker #41
No reviewers
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/backstage!41
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/quality-gates-22"
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?
Summary
Adds the missing application quality gates as a repository-owned Woodpecker workflow, leaving shared global workflows untouched.
.woodpecker/application-checks.yamlruns on pull requests and on pushes to the default branch (excluding Markdown and the generated catalog file):node:24-trixieplus Python 3, using the checked-in Yarn release and--immutable.yarn tsc.yarn lint:all.yarn prettier:check.yarn test:ci --runInBand, bounded by a 15-minutetimeoutthat emits a dedicated error before failing.yarn build:backend.Each check is a separate, named step, so the failing gate is obvious. The workflow is named
application-checks, which keeps its results distinct from the globalpr-reviewworkflow that still runs alongside it.The workflow needs no
FORGEJO_TOKENand never runssync:forgejo, so it is independent of live Forgejo data. It uses the declared Node 24 engine and the vendored Yarn 4.18.1; the Bun migration remains #20.Validation
woodpecker-cli lint .woodpecker/application-checks.yaml— validinstall --immutable— passtsc— passlint:all— passprettier:check— passtest:ci --runInBand— 1 suite / 1 test passbuild:backend— passtimeoutwrapper returns 124 and reaches the explicit timeout message.Closes #22