Skip to content

Give Forge one owner for each status comment #16

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.

Sign up for GitHub

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

Merged
numinousmuses merged 1 commit into from
Sep 6, 2026
Merged

Give Forge one owner for each status comment #16

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 5 additions & 3 deletions .forge/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ its independently recorded checks.
agent reports its plan and useful discoveries as it works. A verified candidate
becomes a draft PR for review, with separate checks on the proposed merge.
- **Scheduled check:** Each occurrence updates the same status comment in its
tracking issue. The latest result and a short recent history stay together.
tracking issue. The latest result replaces the previous result.

```mermaid
flowchart LR
Expand All @@ -29,7 +29,8 @@ flowchart LR

One Forge status comment answers **where are we now?** It is edited as work
progresses and when checks finish. It explains the current finding and next
action, with recorded checks and recent activity in a collapsed section.
action, with recorded checks in a collapsed section. Full run history stays in
execution records; the comment shows only the current state.
New commits reuse that comment. Routine updates do not add notifications.
Agent observations are distinguished from recorded verification.

Expand All @@ -40,7 +41,8 @@ review details; no separate Forge dashboard is required.

Maintainers choose scope, resolve behavior questions, and decide what merges.
CI verifies a contributor's code without automatically modifying it. Ordinary
comments do not trigger additional engineering work.
comments do not trigger additional engineering work. One service owns Forge's
single status comment. The CI workflow reports checks and cannot post comments.

## How Forge communicates

Expand Down
10 changes: 5 additions & 5 deletions .forge/communication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,13 +10,13 @@ When a candidate is ready, explain the change and remaining concerns. When
independent checks finish, distinguish observed results from untested claims.

Keep one status comment per issue or PR and edit it in place. Its current
explanation must stand alone. Put check details and a short recent activity
history in a collapsed section. Reuse the comment across new commits and
explanation must stand alone. Put check details in a collapsed section. Keep
activity history in execution records, not in the comment. Reuse the comment across new commits and
scheduled occurrences. Completion updates the comment and check status.

Reserve separate replies for an explicit question or a decision that requires
a person. Put actionable code findings in a review attached to the relevant
code. Do not post tool-by-tool narration or routine milestone announcements. When a run
Put questions, decisions, and findings in that same status comment. Do not add
separate automatic replies, task summaries, or completion announcements. Human
discussion remains separate. Do not post tool-by-tool narration. When a run
fails or is interrupted, say what remains unresolved. Never invent a finding
just to make an uneventful run sound productive.

Expand Down
Loading
Loading