GitClear

Hello PH family, If you ever worked as a developer you know how hard it could be to have a clear idea of all the tasks that need to happen on a project. Between the code reviews, the tech debt, and the bugs it could be a real mess. Gitclear help you out with code reviews, so you focus only on the things that matter. As a manager you see the great picture, and don't have to micro-manage.all the dashboards are here you keep informed. Hope you like it!

Hello, product hunters! Last time we featured our product on here, it had a different name and far fewer capabilities. 3 years later, we're very excited to bring you GitClear v4 🥳, marking the release of a free subscription plan 🤯, integration with Google's DORA framework, the tech debt inspector and a brand-new community page! 🔹 GitClear computes a single, reliable metric called "Line Impact" Line Impact measures the approximate cognitive load necessary to make a change to a project, by taking into account common operations (line additions, removals, duplicated code etc.) in their respective context (such as file type, commit size and code churn) and computing a numeric score. Here are some of the coolest things that result from this measurement: 🚀 When you start measuring the total Line Impact your team produces in a day, you get the project velocity 🐌 Plotting the daily Line Impact and breaking it down by subprojects can help you identify where tech debts tends to accumulate 👩‍⚕️ Correlating developer output with individual directories of your project lets you find the domain experts of your team 🔹 Are you a developer? The fastest code to review is the code you skip over. GitClear helps developers skip about 30-40% more code than conventional diff viewers by recognizing auto-generated code, copied and moved lines and find-and-replace operations. Additionally, we look at how code changes across multiple commits to identify groups of changesets and demarcate lines that change in further commits. 🔹 Are you a leading a team of developers? Our Commit Activity Browser pulls data from Jira and Git to show you what the team is working on, no interruptions. The Domain Experts report reveals what each person specializes on. The advanced historical stats we generate provide an overview of which developers are struggling, when the most productive times for your team are, and when interruptions occur. 🔹 What's new in GitClear v4? Here's how this update looks like, as measured by GitClear itself: ▪️ Full, automatically configured, Google DORA integration; ▪️ Second generation stats on pull requests; ▪️ The Tech Debt Inspector; ▪️ Teams 2.0: better clarity, easier invitations; ▪️ Commit Activity Browser v3: remember your position in the midst of reviewing ad hoc commit groups ▪️ And some of the biggest changes since our last ProductHunt post: Jira issue stats & integration with Story Points, improved per-developer stats, GitClear on-prem, notifications, developer code reactions. Head over to our blog to learn more! 🔹 GitClear is FREE for hobbyists! Among the GitClear v4 news, this one we are most excited about! If you are a solo developer pursuing a better code review tool and more repo clarity, sign up for the free GitClear plan! 🔹 Wait, so why is Line Impact better than existing dev metrics? We're so glad you asked! Here's a short questionnaire to decide if GitClear is useful for your team: ▪️ When measuring how code evolves in a project, does your metric of choice account for language verbosity, moved code or no-ops? ▪️ What about measuring how many lines of code eventually get discarded? ▪️ Or monitoring accumulating tech debt? ▪️ Can you normalize commit and issue frequency such that scores don't get increased artificially? ▪️ Does your metric distinguish between desirable (code polish) and undesirable code churn? ▪️ If we've managed to poke a hole into your existing solution and you'd like to learn more, we talk about Line Impact at length on our blog 🔹 But can't developer metrics be abused by managers? GitClear should not act as a tool for evaluating developers! We designed Line Impact as a configurable way to measure how the code base of a project evolves with time. We encourage collaboration between leaders and developers to customize the way Line Impact is computed, in order to make the tool fit the project as well as possible. Read more here. 🔹 We want to hear your feedback! Sign up for GitClear here and tell us your thoughts via ProductHunt or the recently released community page!

Can't wait to hear what people have to say about our revamped product! If you have any ideas for future product videos, we're collecting those as well! I am going to be trying to launch a new video or two every week for the next while, to help everyone get a sense for how many interesting ways this set of tools can be used to make for a happier dev team.