Handle fixes transparently
Easily add, track, and announce last-minute fixes to ensure full visibility
You can add a fix from within Runway on a given releaseâs feature readiness view, either creating it from any item that already appears on the working branch or using an explicit â+ Add a fixâ action. Or, take advantage of a new /runway add fix slash command to create a fix on the fly, without leaving Slack.
Full explanations for late changes
Ensure clarity and standards with mandatory justifications for late-stage fixes
Wherever you create a fix, youâre prompted to include additional details on the fix and why itâs needed. This context is surfaced alongside the fix and helps your team build a culture of accountability and standards around what kind of work should actually be allowed to enter a release late in the cycle.
Set approval flow for fixes
Protect releases with built-in approvals for late-arriving changes
Apply actual guardrails to your fixes by optionally enabling an approval flow that each and every fix must go through. With the approval flow enabled, new fixes are highlighted as âpending approvalâ in the releaseâs feature readiness view. Pending fixes must be reviewed and can be either approved or rejected by certain folks on your team. You can also enable GitHub status check. If enabled, these status checks will appear on any PRs open against the release branch and they will only pass if and when the associated fix in Runway is approved.
Track fix requests over time
Gain insights into your teamâs handling of last-minute release changes
In order to improve your teamâs practices around late-arriving work and release stabilization, itâs helpful to track things like how often potential fixes are being raised, how often theyâre actually pulled in, and how much of a given releaseâs diff is made up of these late items. Runway collects metrics like these as you work and surfaces them per release, as well as at an app and org level.
Auto cherry-pick PRs
Seamlessly manage cherry-picks from PRs into release branches
Any PR that contains a designated, customizable pattern in its title will be actively monitored by Runway â as soon as itâs merged into the working branch, Runway will cherry pick the relevant commits and open a PR against the specified release branch. If you also have the âmerge Runway PRsâ automation enabled, the fixes will be auto-merged once required checks pass â thereâs nothing more your team needs to do.
