Our customers made these suggestions for improving GitClear. Suggestions for improving GitClear.

Allow customer access to a REST API to get the data from GitClear reports progamatically

Create a version of GitClear that can be downloaded to a client to calculate the Line Impact of a prospective job candidate (without uploading any of their sensitive ...

Allow code comments to have formatted code highlighting

We currently show Line Impact associated with issues vs not, but we don't yet have a clear depiction of what percent of a team's work is spent on unplanned tasks. For ...

Add dark mode to all GitClear reports (not just the historical report and CAB report)

This is already done to some extent, but here are a few ways in which interpreting code semantically could improve the approximation of dev cognitive effort. This ...

I just want to see if I'm winning per day, week or year, etc. If you could just display line impact in a sorted list by user that would be very helpful Past ...

Current PR stats talk about the volume of comments, but they don't offer much signal to differentiate whether the comments being received are *useful* or distracting? ...

Under the "Release Tracking Section" add an option to submit a Regex to identify release branches. Ex: Organization use the Git-Flow (AVH) and Release branches are ...

Currently, upon login or clicking the GitClear logo after being logged in, we always direct the user to the Commit Activity Browser. For this item, we would allow ...

GitClear's Commit Activity Browser already allows viewing arbitrarily grouped commits with responses and follow-up action. It wouldn't be much more work to create a ...