Investigate and communicate shipped work with repository evidence.
Give d5s agents scoped GitHub access for repository research, pull-request context, issue preparation, and release communication.
What agents can do with GitHub
GitHub supplies the implementation evidence behind engineering workflows. A d5s agent can inspect repositories, commits, pull requests, and issues in an isolated run, then prepare reviewable work. Token scopes and operating policy still bound what the agent can change or publish.
- Read repositories, commits, and pull requests
- Prepare issues and release evidence
- Trace changes without exposing unrelated credentials
Available connection methods
One public brand can have more than one verified access method. Pick the method that matches the workflow and credential policy.
API connection
API · oauth2 or static_token
Read and write GitHub repos, issues, and pull requests.
Example compositions using GitHub
These examples show how the connector can participate in recurring work; they are patterns to build in d5s, not preinstalled workflow objects.
Incident triage
Trace a production error, identify the likely change, and prepare a triage issue without giving the agent authority to modify production.
Release notes
Collect shipped changes, translate implementation detail into customer outcomes, and route a complete release-note draft for approval.
Try asking
Connect GitHub to a governed workflow.
Tell us what your team repeats today. We will map the systems, approval boundaries, and first governed run with you.