docs: clarify CI trigger behavior in wake-up documentation #1123
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![codegen-sh[bot]](https://avatars.githubusercontent.com/in/321279?s=60&v=4){kind=small}
- Add info box explaining Codegen starts immediately when first check fails - Add info box explaining all failed checks from same commit route to single agent - Makes customer-facing docs more intuitive and clear about timing behavior
|
I see a check failed - I'm on it! 🫡 |
- Removed stray </initial_code> tag at end of file - This was causing test failures in the CI pipeline
|
✅ Fixed the failing check in commit 0b78983. The issue was a stray The CI should now pass! 🚀 💻 View my work • React 👍 or 👎 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the wake-up documentation to clarify two key aspects of how Codegen responds to CI failures:
Changes Made
Why This Matters
The previous documentation didn't clearly explain the timing behavior, which led to customer confusion about when Codegen would start working on failed checks. These additions make the customer-facing docs more intuitive and remove technical jargon while providing clear expectations.
Files Changed
docs/capabilities/wake-up.mdx- Added two info boxes in the "What Triggers Wake Up" section💻 View my work • About Codegen