GitHub
Link pull requests and issues to change control in Seal.
Put this connection to work Read the platform connection docs
Connect the code change to its review and test evidence.
Agree the records and transfer direction for this job, then connect the evidence to the work your team needs to review.
GitHub
Software change review
- Change references and verification evidence
- Missing or unmatched information
- Next steps for your team to review
What’s connected.
Leverage Seal's dedicated GitHub app for robust, GxP-compliant change control. Automate the linkage between Pull Requests and formal Change Orders, enforce review workflows based on risk, sync GitHub Issues with your QMS tasks, and maintain a complete, auditable history of software changes directly within Seal.
Connection setup and permissions
Use the dedicated Seal application. Review the permissions and installation requirements for your environment before connecting.
Related blueprints
Before it goes live.
Access and write-back
Reading records and writing back are separate decisions. Define which records are in scope, whose permissions apply and which changes require 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.