Skip to content

Explain Forge progress and review states - #9

Merged
numinousmuses merged 4 commits into
masterfrom
docs/pr-progress-guide
Sep 6, 2026
Merged

numinousmuses merged 4 commits into
masterfrom
docs/pr-progress-guide

Conversation

@numinousmuses

@numinousmuses numinousmuses commented Sep 6, 2026

Copy link
Copy Markdown

Explain how contributors follow Forge work on a PR and respond to failed checks. The guide separates agent progress from independent verification, links readers to the tested revision and results, and keeps merge decisions with maintainers. The generated status formatter also distinguishes a proposed change passing checks from PR verification and identifies tasks that end without a patch.

flowchart LR
 subgraph Before
  A[Contributor opens PR] --> B[Guide lacks next steps for progress and failures]
  C[Task produces no patch] --> D[Generic blocked message]
 end
 subgraph After
  E[Contributor opens PR] --> F[Guide explains updated verification comment]
  F --> G[Inspect failure and push a correction]
  F --> H[Follow an attached engineering task separately]
  I[Task produces no patch] --> J[Explicit no-change outcome]
 end
Loading

Validation: real PR verification reported an intentional test failure, then a passing corrected revision in the same comment. The temporary test was removed. An attached engineering task progressed through a recorded revision and independent protocol/documentation checks; its patch was applied only after its hash and Git tree matched the verification record. The final wording and generated workflow receive fresh required PR checks before merge.

@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown

Numinous Forge · PR verification

Verification passed

The accepted checks passed. Ready for human review.

This run checks the PR; it does not modify code.

Checks passed: Protocol, Documentation.

Revision: 69ebc779cbfe. Tested merge: 9d2660dd056c.

Open workflow and results · Task cec2fa2f1f643bdd67c8c3cb567be31b

Last observed 2026-09-06 06:10 UTC. This comment updates as work progresses.

@numinousmuses

numinousmuses commented Sep 6, 2026

Copy link
Copy Markdown
Author

Numinous Forge · Engineering task

Verification passed

The proposed change passed its accepted checks. PR verification is reported separately.

Checks passed: Protocol, Documentation.

Source revision: f785a0d424c8.

Open pull request · Task 13e5fe795929b369669dc4d329fc4053

Last observed 2026-09-06 06:04 UTC. This comment updates as work progresses.

@numinousmuses
numinousmuses marked this pull request as ready for review September 6, 2026 06:06
@numinousmuses
numinousmuses merged commit 5ac4959 into master Sep 6, 2026
2 checks passed
@numinousmuses

Copy link
Copy Markdown
Author

Numinous Forge · Change and verification

Result: PR progress comments added and merged into this fork. Contributors can follow work in the PR conversation.

What changed: One verification comment updates as checks queue, run, fail, or pass. An attached engineering task has a separate progress comment, so preparing a change and checking that change are distinguishable.

What we exercised on this PR:

  • An intentionally failing test produced a failed verification comment.
  • Removing that test and pushing a correction updated the same comment to a passing result.
  • An attached task initially produced no patch, which was reported explicitly. A revised request produced a documentation change that passed independent checks.
  • The final PR revision passed protocol and documentation verification before merge.

How to use it: Push a commit to rerun PR checks. Read the current verification comment for the result and workflow link. An attached task's comment reports its own progress. Maintainers still review the behavior and decide what to merge.

These change summaries explain the work and its test evidence; the separate progress comments report current execution state.

Review summary for 69ebc779cbfe. Live task and CI progress are reported separately.

@numinousmuses numinousmuses added the trigger:ci Forge was triggered by a contributor PR or new commit. label Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

trigger:ci Forge was triggered by a contributor PR or new commit.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant