It’s another monthly burst of news about bors-ng, a CI service that helps you enforce the “never break the build” policy in your GitHub repositories.

In the last month, we landed 24 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

  • notriddle optimized bors for server with lots of projects that are mostly idle, which is the state for most of the public instance’s users
  • alsuren fixed a bunch of compiler warnings
  • zealousidealroll added support for wildcards in status configuration
  • iagomoreira made bors produce an error when you misspell it “bros” 👊
  • notriddle worked around an old bug that could cause canceled patches to wind up starting builds with no patches in them

New Contributors

Want to see your name in this newsletter? Look at bors starters, a curated list of issues that are good for new contributors!

Who’s using bors?

This month’s featured user is Amethyst, a data-oriented game engine. It’s massively multithreaded, memory safe, and based on an Entity—Component—System architecture to achieve good cache locality and separation of concerns.

Amethyst uses bors with their thirty-eight thousand line-of-Rust-code monorepo. Bors is also used by many of Amethyst’s dependencies, such as gfx, specs, and ron. All of them support Windows, Linux, and Mac, and have been adding support for more (such as iOS).

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