Track staging work in Factory with durable Linear links - #22
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
1 participant
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.
Merged PRs on staging can be missing from Releases before a frozen candidate exists. This read-only reporter sends staging source and deployment observations to Factory, which reuses linked Linear issues or creates one deterministic pilot tracking issue. Scheduled reconciliation recovers missed events without duplicate issues.
The reporter is delivered to master and always checks staging. It executes reviewed master code with read-only GitHub metadata permissions and a short-lived identity tied to this exact repository, workflow and branch. It does not deploy the app or dispatch review bots, QA, regression or promotion.
Factory owns the receiver, configurable Factory Lab pilot mapping, durable queue and Releases UI. See the coordinated change record and intake guide.
Validation: collector Node syntax and workflow YAML parsing passed. Existing owner CI is preserved. Factory's source/authentication and persistence suites cover exact source/deployment identity, duplicate/lost events, human status conflicts and Linear writes. No public product fields, application source, package or backend artifact changes.