It’s another monthly burst of news about bors-ng, a workflow tool where you only merge feature branches were you know that they won’t break master after the merge.

In the last month, we landed 5 PRs in the bors-ng repository.

“This Month in Bors” is written in public on GitHub. If you find a mistake, pull requests or issue reports are appreciated!

Notable Additions

• kimsaehun added an option to make a PR not batch
• notriddle added checks to make sure only one runner process per repository ever exists
• pksunkara improved the performance of the pre-run checks

New Contributors

• Pavan Kumar Sunkara (@pksunkara)

Want to see your name in this newsletter? Contribute on our GitHub repository.

Who’s using bors?

This month’s featured user is rust-analyzer, an experimental compiler frontend for the Rust language.

The compiler frontend performs all of the language-specific work before code generation itself (primarily, this means parsing the code, building a symbol table, and checking types). The Rust Analyzer is specifically designed for IDE use, so it acts as a testing ground for analyzing syntactically ill-formed programs, incremental analysis, and performance optimizations within the compiler.

Got any suggestions for next month? Post a comment on the March pull request.