Chances are you've felt pain around deploying changes to production. Deployments cause stress and anxiety for everyone involved, especially when they happen infrequently.
Today, we’re releasing Ready to Deploy — a feature that provides visibility into apps with a backlog of changes waiting to be deployed. We built this feature to help ease deployment pain for engineering teams. You can see all of your team’s merged pull requests, organized by repository and sorted by how long they’ve been awaiting deployment.
✨ What’s new?
- Undeployed PRs: see the number of pull requests ready to deploy for your team.
- Merge to deploy: see which repositories have the longest average time between merging and deploying pull requests.
- Time to deploy goal: set a goal for time to deploy to prevent changes from piling up right before pushing to production.
- Visibility from open to deploy: track work in progress all the way from code review (using the Open Pull Requests view) to deployment (using the Ready to Deploy view).
- Advanced filters: filters allow you to change the data range and choose whether to include or exclude pull requests created by bots (e.g. Dependabot).
💭 How does it work?
- Go to our Ready to Deploy feature to see your data. It works out-of-the-box with our existing GitHub integration if you’re using GitHub Actions, deployments, or releases.
- We automatically detect how you deploy each repository, but you can also manually assign specific workflow runs, check runs, deployments, and releases as production deployments for each repository.
👋 Latest from the community
- Omar Bahareth, CTO at Ejaro, wrote Engineering Management: An Overview, a deep dive into the most important responsibilities of engineering managers.