docs: keep GitHub comments concise (#11447)
Signed-off-by: Jasper Hugo <jasper@jasperhugo.com>
This commit is contained in:
@@ -16,6 +16,15 @@ The issue is the source of truth for work intended for an upstream pull request.
|
||||
|
||||
Maintainer-directed work, urgent security fixes, release automation, and local or exploratory changes do not require a Ready issue.
|
||||
|
||||
## GitHub Communication
|
||||
|
||||
Write issue and pull request comments for humans, not as exhaustive work logs.
|
||||
|
||||
- Lead with the conclusion or action needed.
|
||||
- Keep comments concise; do not repeat context already present in the thread.
|
||||
- Use short paragraphs or bullets, and include implementation details only when they affect a decision or review.
|
||||
- Prefer one clear summary over multiple incremental comments.
|
||||
|
||||
## Agent Loop Migration
|
||||
|
||||
We are replacing the legacy agent loop in `crates/goose/src/agents/agent.rs` with the state machine in `crates/goose/src/agents/state_machine/`. The state-machine path is enabled with `GOOSE_STATE_MACHINE=1`.
|
||||
|
||||
Reference in New Issue
Block a user