Connect the code change to its review and test evidence.
Neil
- Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
- Reads
GitHub
- Returns
- Change references and verification evidence
- Missing or unmatched information
- Next steps for your team to review
1What’s connected.
The Seal Change Control GitHub App creates a Seal change record from a configured template when a matching pull request opens, and updates it as the pull request changes. It adds a commit status linking to the record, and can approve or close the pull request when the record is approved or rejected. Seal support provisions the app; merge and deployment stay in your delivery workflow.
Connection setup and permissions
Use the dedicated Seal application. Review the permissions and installation requirements for your environment before connecting.
Related blueprints
2Hold the merge until the Seal change record is approved.
Route
A commit status, set to error, failure, pending or success, shows on the pull requests that contain the commit, and its target URL is linked from GitHub.¹ A status’s context names the system that set it. The combined status of a ref is failure if any context reports error or failure.¹ Statuses differ from checks: GitHub Actions workflows produce checks, not commit statuses.²
Merge rules
A protected branch or a ruleset can require status checks before a merge, and a required check can be either a check or a commit status.³⁴ A required check can name the app expected to set it; a status set by anyone else then blocks the merge.³
Revisions
A review is tied to a commit SHA, and without one it applies to the pull request’s latest commit. A protected branch can dismiss approvals that new commits make stale.⁵³ The pull_request webhook sends synchronize when the head branch is updated, and closed with a merged flag that tells a merge from a close.⁶
When it fails
- A pull request merged before the record was approved
- Only required status checks must pass before changes reach a protected branch.³ Make the Seal status a required check on the protected branch, with the Seal app as its expected source.
Check one record
Open a test pull request against a protected branch. A Seal change record should appear from its template, with a commit status linking to it. Push a new commit and confirm the record updates. Approve the record and confirm the pull request is approved.
3Start with the job.
Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.
4Before it goes live.
Access and any write-back
Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.
