Show Forge progress directly on pull requests - #8
Merged
Merged
Conversation
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.
Show Forge progress directly on pull requests with one updated verification comment. The comment identifies the revision, phase, checks, and result link. New commits are checked automatically; reporting failures and superseded results cannot produce a passing status. Engineering tasks can also have a separate progress comment.
Keep the public walkthrough focused on demonstrated changes and review evidence. Internal deployment reports remain in the private platform repository, and public receipts omit model details.
Validation: platform race tests and Python reporting tests; real HTTP tests cover updates, pagination, spoofed markers, privacy, and stale revisions. The workflow executes trusted default-branch code. This PR runs the existing required checks; after merge, a follow-up PR exercises the new reporting path.