Give Forge one owner for each status comment - #16
Merged
Merged
Conversation
Author
Numinous Forge · Merged into this forkTrigger: CI This PR has been merged. The recorded checks passed on its reviewed revision. Next: No further action on this PR. Verification details
Source revision 05f6bfd255d9. 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 now has one writer for each issue or PR status comment. The workflow only submits work and reports commit checks, with read-only PR access. The alternate task reporter and comment finalizer are removed. The comment replaces its current explanation and shows verification details without an appended activity timeline.
This PR installs the workflow change and updates the guides. It also checks for a changed PR head during polling independently of comment reporting, so an obsolete workflow does not hold up the latest revision.
flowchart LR subgraph Before A[CI workflow] --> B[Optional progress writer] C[Task reporter] --> D[Separate task comment] E[Conversation service] --> F[Current status with old updates] end subgraph After G[CI workflow] --> H[Task submission and commit checks] H --> I[Conversation service] I --> J[One edited status comment per issue or PR] endValidation: platform tests cover routine transitions, publication, merge, new commits, schedule occurrences, lost acknowledgments, ignored legacy milestones, and rejection of comment access from CI. Fresh issue and scheduled runs are being observed from their first update. The configured checks on this PR cover Darkbloom protocol and documentation, not the Forge platform itself.