Vibinex Code-Review
source link: https://www.producthunt.com/posts/vibinex-code-review
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Support is great. Feedback is even better.
"Thanks for checking out our launch and we eagerly wait for your feedback. We would love to know what issues your team faces related to the PR review process.Please connect with us at [email protected] or on WhatsApp using this link: https://wa.me/918511557566."
Hey everyone! Super excited to finally launch our pull-request tool today.
A few months back, as a software engineer myself, I set out to fix the most frustrating problems and elevate the development experience of all software engineers. Across several companies, the most frustrating yet critical part of leading a project was setting up the code review process and getting it adopted.
With Vibinex, we are making that extremely frictionless and efficient.
The core feature of Vibinex is the automatic distribution and assignment of code reviewing using git history. This changes the review process from being binary (approved or not approved) to continuous (e.g. 20% approved).
Some ways in which this empowers developers:
1. Identify which PRs require your review: Going through 10 PRs is a hassle. But reviewing 2 PRs that require your attention is easily manageable. 2. Partially review a PR: You don't need to review every diff in a PR, just the code-hunks that are relevant to you. With Vibinex, you don't have to worry about miscommunication. 3. Better awareness: With this new process, you review everything relevant to you in lesser time. So you never have to worry about communicating outdated information about the product to your stakeholders.
PRIVACY FIRST For doing all this, we don't even ask for access to your code. Our open-source Rust program (Code: https://github.com/Alokit-Innova...) runs in your CI pipeline, parses your git history to extract only the relevant metadata (making it impossible to reproduce your code from it), and then SHA-encrypts every word in it, including your email aliases, making them unreadable, and only sends that to our servers.
When you log in using our browser extension (also, open-source: https://github.com/Alokit-Innova...), we get your email aliases and match their SHA-encrypted version with the data from our backend to show you the insights.
COMPATIBILITY: Code hosting: Github and Bitbucket Browsers: Chromium-based (Google Chrome, Microsoft Edge, Brave etc.)
Note: If your team uses a different code-hosting service or web browser and is keen on using our tool, we'd be happy to build the integrations to get you started.
@irina_haupt We current assign code blocks based on the history of the code itself, i.e. the last editor of that piece of code.
But in the future, we'll extract deeper insights (like active developers, module owners & production logs etc) to enhance this distribution algorithm further.
If you have any more ideas, we'd love to hear them.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK