Sourcery

Old PRs are a treasure trove of information about a code base. They show how a code base has evolved and they also can give insight into what a team does (and doesn't) care about during code reviews. A few weeks ago we added customisable review instructions to Sourcery to let you tell us what to look for or not to worry about during code reviews. Now we're working on using past peer reviews to create those review instructions automatically. We're able to look at past code reviews, find patterns in them, and suggest rules that you might want to use for your code reviews moving forward. Here are a couple of the rules we found when looking at our own codebase history and one of those rules in action in a code review from a few days ago. These generated instructions are still in a closed beta, but let me know if you'd want early access to try it out!

The Sourcery team have been rolling out so many improvements to our code reviews over the past couple of weeks that I've been falling behind in my updates! Here are a few of the highlights: 1️⃣ Hello, GitLab! 🎉 Sourcery now supports GitLab and can review any of your MRs 2️⃣ Immediate Reviews in Your IDE 💻 You can now request code reviews directly in your IDE before committing your code, shifting code reviews even further left. 3️⃣ Customizable Reviews 🛠️ Every code base is unique, so we've made it possible to customize reviews to fit your team's style guide, code standards, and best practices. 4️⃣ Review Summaries and Guides 📚 Each PR now has a review summary and guide to give you insights on every change made to a PR. Quickly understand what’s happening in your code. What do you want to see us add next?

We've been playing around with different ways to validate and test LLM responses to help us move faster. It turn out one of the best approaches is pretty simple. Creating unit tests for the LLM responses - https://lnkd.in/e7pyMwr6