Skip to content

docs: clarify CI trigger behavior in wake-up documentation #1123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/capabilities/wake-up.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,14 @@ Wake up activates when:
- **Test Failures:** Unit tests, integration tests, or automated test suites fail
- **Code Quality Issues:** Static analysis tools report violations or warnings

<Info>
**Immediate Response:** Codegen starts working as soon as the first check fails - it doesn't wait for all checks to complete.
</Info>

<Info>
**Single Agent Per Commit:** All failed checks from the same commit are handled by one agent, ensuring consistent fixes across all failures.
</Info>

## The Auto-Fix Process

When Codegen wakes up to fix a failing PR, it follows this process:
Expand Down
Loading