Fixes

Fixes are work items that aren't yet in on the release branch, that your team would like to pull into the release – these can either be open PRs against the working branch, or PRs or commits that have already been merged into the working branch.

Configuring fixes

Within Settings > Fix Requests, there are a number of different configurations to customize how fixes work for your team:

• Fixes for open PRs

  • Create a fix for all open PRs against the release branch

  • Disallow new fix requests once release is submitted

  • Thread related fix notifications

• Fix approvals

  • Fix approvals enabled: if enabled, then all fixes must be approved by a teammate with the relevant permissions in order for the fix to be included in the release

  • Number of approvals required

  • Status checks enabled: if enabled, Runway will include a status check on any pull requests created for fixes going into the release branch. The status check will only pass when the fix request associated with the PR has been approved

  • Require fix approvals during specific windows only: if enabled, Runway will start requiring approvals for fixes created at the time, or after, the configured window begins.

• Fix request form template

  • Fix request form fields: in addition to configuring the fields that your teammates should fill in when requesting a fix, you can also set a minimum character limit and indicate which fields are required or optional

• Auto-merge fixes

  • Auto-merge user-created PRs with fixes enabled: if enabled, user-created PRs with fixes against the selected target branches will be automatically merged if they are approved and have no conflicts

Fixes settings

• Create fixes for open PRs against the release branch: Runway will automatically create a Fix for any PRs that are opened against the release branch.

• Fix approvals: If enabled, work items designated as fixes will surface an approval status. Team members with sufficient privileges can approve or reject fix requests. Approvals can be performed on the Feature readiness release step.

Runway will only auto-merge cherry-pick PRs against open against the release branch if the fix has been approved in Runway. The following conditions must be true for this behavior to apply:

• The "Pull fixes into the release" automation and Fix approvals is enabled

• The "Merge pull requests created by Runway" automation is enabled

• "Fix approvals" are enabled

• Add pull request GitHub status check for fix request approvals: Runway will include a status check on any pull requests created for fixes going into the release branch. The status check will only pass when the fix request associated with the PR has been approved.

• Thread related fix notifications: Notifications relevant to a given Fix will be threaded in Slack.