ci: require Woodpecker yaml; stop treating it as architecture non-goal #6
No reviewers
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!6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/woodpecker-required"
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
.woodpecker.yamlas if CI were app scaffold. Org rule is the opposite: missing config isNO_CI_MISSING_WOODPECKER(CAC #154).cl8y-forgejo“do not add a Woodpecker agent to Forge Compose” is a real ops constraint and was not changed.Closes #5.
Test plan
git ls-filesincludes.woodpecker.yamland.gitleaks.tomlci/woodpecker/pr(and push) go green: gitleaks + treedrain skip: no occupying job for rebase/fix-pr/CI-wait; remaining continue
drain skip: default autoland requires tip ACCEPT (#77)