Connect the code change to its review and test evidence.
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.
GitHub
Software change review
- 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
2Start 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.
3Before 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.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
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.