Keep Forge progress in one GitHub status comment - #13
Merged
Merged
Conversation
Author
Numinous Forge · Merged into this forkThis PR has been merged. The recorded checks passed on its reviewed revision. Next: No further action on this PR. Verification details
Source revision 2678801b6e7b. Verification status comes from execution records; agent observations are provisional. This run verifies the PR and does not modify its code. |
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
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.
Forge progress now stays in one updated status comment per issue or PR. Check details and recent activity are collapsed beneath the current explanation, and the guide links directly to the GitHub engineering board.
These pages describe the deployed communication behavior. This PR exercises automatic verification and its status comment. Its configured protocol and documentation checks do not test Forge's comment service or lint these
.forgepages.flowchart LR subgraph Before A[Service.update receives progress] --> B[New milestone comment] B --> C[Separate overview links to milestone] end subgraph After D[Service.update receives progress] --> E[GitHub.status edits one comment] E --> F[Current explanation and collapsed checks] D --> G[Project card follows recorded state] endValidation: reviewed both guides and their board link;
git diff --checkpassed. The platform regression test reproduced five comments for four transitions before the change, and one afterward. The platform suite passed 97 Python tests and the Go checks. Live verification of this PR will establish whether the deployed integration updates its comment and board card correctly.