Aviator - June updates

batching PRs, title and body validation, simplified merge rules and more.

Highlights

• 🌟  Aviator Launch!

• 🚀  Batching in parallel mode - merge PRs in batches

• 🚀  Validation for PR title and body

• 🚀  Simplified merge rules page

• 🚀  Stacked PRs open beta

• 🚀  ChangeSets are now available to everyone

🌟 Aviator Launch

We officially launched Aviator on May 24th, check out our blog post in case you missed it! Give us a follow on Twitter or LinkedIn for other announcements, and we would love to feature you on our home page, ask us how.

New features

Batching

We are introducing batching to increase the throughput of PRs merged by merging more PRs per CI run. This is available in parallel mode.

See our docs for more details on how to configure your settings and start batching your PRs.

Batching PRs in parallel mode

Validation rules for PR title and body

Using the new preconditions, you can specify regexes to validate the title and body. For instance if you want each PR title to have a ticket number, or if you have a checklist of items in the body.

preconditions:
	validations:
    - name: missing JIRA ticket in PR title
      match:
        type: title
        regex:
        - -\\s\\[[^\\]]*\\]
        - ()
    - name: validation_body
      match:
        type: body
        regex:
        - -\\s\\[[^\\]]*\\]

Simplified Merge Rules page

We have simplified our Merge Rules page to a few basic settings. Using the Merge Rules UI is only recommended for a quick setup. The advanced configuration options will only be supported through the configuration file. You can define that YAML file in your GitHub repo or through the Aviator Merge rules dashboard. Please see our documentation for more details.

Updated real-time pending checks

In our last update, we added real-time pending status checks for the first PR in the queue. We have now added real-time checks for all PRs in the queue. To avoid noise for repos with many status checks, we will only show any pending or failed tests in addition to the number of passing tests. The status check name is also linked to the corresponding build URL.

Stacked PRs public beta

Stacked PRs is a way of structuring your pull requests that optimizes for small individual PRs (easier and quicker review for your teammates!) and development velocity (you don’t have to wait for review before working on the next part of your feature!).

With Stacked PRs, you’re able to structure your changes as a series of smaller PRs that build on each other, and Aviator makes it easy to keep them in sync (if your first PR in the stack changes, we need to make sure all of the later PRs in the stack reflect that change as well) and easy to merge.

Check out our Stacked PRs Getting Started Guide if you’d like to try it out, and please reach out.

Bug fixes and improvements

• Added support for Google SSO for on-prem

• Show aggregate metrics in Analytics page (p50, p75, p90, p100) for Time in Queue

• Fixed lag in processing queue after adding skip label

• Fixed a bug causing duplicate draft PRs if a skip label is added

• Fixed analytics page off by 1 day error

• Restricted reset button to admin

• Improved error messaging for unsupported base branches

• Parallel mode now works with the concurrency GitHub Actions workflow configuration

• Better handling of GitHub rate limiting and timeout errors.

Questions or comments? Please reply back here, we would love to hear from you.