cblavier
We tried Sourcery, a GitHub integration that posts instant AI-based code reviews on our pull requests.
I was pleasantly surprised by how relevant the code reviews were ![]()
Some excerpts:
Please let me know if you
- have ever tried such tools?
- have any recommendations for a specific tool?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security












Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
shiroyasha
Never tried out anything similar , but it looks like it could be useful. Just installed it on our repo. My first impression is that is is quite noisy e.g. chore: Convert login page to react by shiroyasha · Pull Request #1638 · operately/operately · GitHub, but maybe I have to get used to it.
Did your team leave all the config options enabled or you made some modifications?
cblavier
Yes it is very verbose and I think we will opt out some options (the generated graph doesn’t seem very useful)
rbino
This could be another alternative:
https://github.com/brave/pull-merge
I’ve never personally tried it but the maintainer is a friend of mine and he told me it’s generic so it should work on any type of repo.
shiroyasha
Reporting back after a couple of weeks of using Sourcery that @cblavier shared. Initially the tool was a nuisance, it generated too much content and interfered with human-to-human communication. We had to silence most of its options, and to add a couple of extra handcrafted prompts to make it behave in a reasonable way.
With those additions, the generated comments started to be actually useful. It is not able to detect larger problems, wrong architecture decisions, but it is good at spotting typos, missing validations, edge cases, etc… It reduces the burden of manual reviews and gives feedback faster to the team.
Overall, the tool is in the nice-to-have category, but not yet in the must-have category.
D4no0
I think this should be highlighted, as this is the silver lining. Such tools are just linters on steroids, even though I doubt they are that consistent, it would be a mistake to assume that they can replace the human factor in code reviews.
I also think it’s also important to point out that this might be a shortcut for companies that never understood how to setup and use already existing static analysis tools like credo (especially with custom made check rules).
dimitarvp
For typo checks you should use GitHub - crate-ci/typos: Source code spell checker · GitHub. I’m using it almost every day and it simply works every time.
It even has a GitHub action if you don’t want to only use it as an offline CLI tool (which is how I use it exclusively but a GitHub action is super useful for CI/CD).
cblavier
We eventually unsubscribed from Sourcery, it was too talkative for our taste.
And a bit too pricey for the value
dimitarvp
I am curious: what would make you pay for automated code reviews? What are the top 3 features that would make you go “I want to have this now”?
cblavier
I can’t answer since I had no expectations for such a tool.
My decision to try it was purely opportunistic and driven by curiosity.
I guess I could pay for it if it was more concise, and 100% accurate (not ChatGPT accurate
)
earonesty
i wrote my own (corerev.q32.com), here’s why:
i want it to:
this:
i use it every day.