Respond to an engineering event
Start work from an issue, change, or deployment signal and gather the context needed to proceed.
Connect engineering systems to workflows that investigate, change, validate, and request approval. Explore example AgentRuntime patterns for GitHub, then confirm connector availability and supported actions before production use.
Use repository and developer-tool events inside controlled engineering workflows with explicit review and recovery paths.
Example architecture only. Exact triggers, actions, scopes, and deployment requirements depend on the connector configuration.
These are representative patterns for the Developer Toolscategory. They are not claims about currently enabled GitHub actions.
Start work from an issue, change, or deployment signal and gather the context needed to proceed.
Let agents investigate and draft while deterministic checks and people control what is accepted.
Keep checks, approvals, notifications, and follow-up actions in one visible run.
Catalog coverage changes. Validate the actual connector build, authentication method, supported operations, and environment requirements with the AgentRuntime team.
Bring the trigger, actions, access constraints, and human decision points. We will map the governed execution path.