fix(ci): do not forbid Woodpecker yaml on architecture #5
Labels
No labels
agent:implement
agent:research
docs
feature
ready
research
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-docs#5
Loading…
Add table
Add a link
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?
Summary
#1 architecture (merged #4) over-blocked
.woodpecker.yamlas if CI were app scaffold. That is wrong.Org rule: missing Woodpecker config is
NO_CI_MISSING_WOODPECKER(CAC #154 / invariant 57). Docs trees get gitleaks + nonempty-tree. Node 24 tests and Playwright stay in #3.Searched sibling local repos: no other product tree had this false “do not add
.woodpecker.yaml” text.cl8y-forgejo“do not add a Woodpecker agent to Forge Compose” is a real ops constraint and stays.Acceptance criteria
.woodpecker.yaml+.gitleaks.tomlexist: gitleaks + nonempty-tree; no Postgres; no Node until #3.ci/woodpecker/*on the PR.Out of scope