How to bring your software delivery workflow into GitHub with agent apps
See how four GitHub Agent Apps can help you scope, secure, roll out, and ship a feature across the SDLC–all without leaving GitHub. The post How to bring your software delivery workflow into GitHub with agent apps appeared first on The GitHub Blog .
Many software engineers have multiple tabs open while reviewing a pull request. A new feature allows users to make the invitation of teammates an optional step during the free-trial onboarding flow. Support has been receiving complaints about this step being a friction point as signups increase. However, by using GitHub agent apps, users can answer key questions about the change within GitHub itself, eliminating the need to switch between different tools.
Before building the change, support questioned whether the "invite your teammates" step correlates with success later in the funnel. They asked the Amplitude agent, and it confirmed that team users who complete the step are more likely to retain, while solo users do not see that correlation. This insight led to a rescope decision: defer the step for solo signups and keep it for team signups. The product insights were available within GitHub, allowing for course correction before any code was written.
While building the change, the Copilot opened a draft pull request. The Endor Labs agent was asked in a comment about any potential issues with the dependencies being touched by the pull request. The agent identified the changed dependencies, checked them for known vulnerabilities and broader package risk, and reported back in the pull request. Everything looked clean, so no remediation was needed. Dependency review became a proactive check while the change was still in front of the engineer.
When rolling out the change, the decision was made to target solo signups with the optional path and keep the existing flow for teams. Feature flags were set up for this purpose. The LaunchDarkly agent created the feature flag and added the code implementation as a commit for review. If the target environment required approval, an approval request was created instead of applying the change directly. The rollout decision still required human input, but the setup process became streamlined.
Before shipping, the code was reviewed for correctness, but the service's deployment state was a separate question. The PagerDuty agent assessed the deployment risk for the pull request against the onboarding service, checking active incidents and recent incident history. The agent recommended whether to proceed with the deployment.
Written by urgent.news from GitHub Blog's reporting — not their text. Machine-written — it may contain errors, so check the original before relying on it.
