docs: add CI courtesy rule to org AGENTS.md
User description
wave-author: eng
Adds a short CI courtesy rule section to the org-default AGENTS.md so every lane follows it: rebuild the same commit once on queue expiry (only with capacity), rebase only for real conflicts (max once/day/PR), and at most 2 open builds per lane on the shared isolated queue.
Refs WAVE-32167.
Summary by CodeRabbit
- Chores
- Added guidance to retry an expired build once when queue conditions allow, then stop and post a note if it expires again.
- Limited rebasing to specific cases and no more than once per day per pull request.
- Capped open builds at two per lane on the shared queue.
CodeAnt-AI Description
Document limits for CI retries, rebases, and queued builds
What Changed
- Clarifies that after a Buildkite queue expiry, contributors may retry the same commit once only when at least 2 agents are connected and the oldest waiting job is under 30 minutes old; if that retry expires, they should stop and post one note.
- Limits rebases to real conflicts or checks that need a newer main, at most once per day per PR.
- Limits each lane to 2 open builds on the shared isolated queue.
Impact
✅ Fewer unnecessary CI rebuilds
✅ Fewer avoidable rebases
✅ Less shared queue congestion
💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
@codeant-ai ask: Your question here
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
@codeant-ai ask: Can you suggest a safer alternative to storing this secret?
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
@codeant-ai: Your feedback here
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
@codeant-ai: Do not flag unused imports.
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
@codeant-ai: review
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.