Ideas for GitClear as submitted to our Feature Upvote board. Ideas are ordered by 'new' and the 50 top matches are included. pr_izjjmrdkltslhmw 2025-05-18T12:19:04Z sug_ft5admaaldo7xnx 2021-12-14T10:17:43Z 2023-03-03T13:16:18Z 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 list showcases examples of when making a specific change to the code *requires* another follow-up change. Usually, the follow-up change is complementary, but does not act in any way to evolve the codebase (not more than the initial change did). Examples: 1. Adding another potential type to an object (should get all Line Impact) vs adding an "else" branch in the section of the code verifying that type 2. Acquiring a synchronization-type object vs releasing it 3. More generally, any resources that need symmetric operations, such as allocating memory in C 4. Extending the db schema of an object to house another column (vs adding that new property to trivial API/method calls on other layers of the app) 5. Creating a new type of Error object/event vs "catching" it in all invocations of the error-triggering code sug_4u64ntz8inxihtc 2021-11-11T15:47:23Z 2023-03-03T13:05:12Z 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? If GitClear could measure Line Impact from commits that occurred in response to PR comments, that could provide a useful lens to glean whether the comments the user leaves are resulting in positive directions. sug_65w3jjqmswkxhig 2021-10-12T00:10:24Z 2023-03-03T12:56:58Z 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 all prefixed with "Release/" or "release/" Having a regex for this instead of a commit message or tag would be beneficial! sug_xj6n5hnaf5b4m6h 2021-09-07T15:26:39Z 2023-03-03T12:46:31Z 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 Month / Week / Date range, etc. 1. - Sam Hamilton - 759 Line impact per day 2. - Roger Fredler - 559 Line impact per day 3. - Roc Vandler - 239 line impact per day. 4. .... 5. ... sug_1vifkodpkvqbg1y 2021-07-22T18:58:13Z 2023-03-03T12:38:37Z 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 this item, we would change that. sug_mvainrhl7whfrdn 2021-07-12T19:04:19Z 2023-03-03T12:37:29Z 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 users to default to whichever report they find most useful sug_tmwt1xqlsugjmzp 2021-07-12T18:54:28Z 2023-03-03T12:37:29Z 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 code to GitClear), such that managers could evaluate a prospective developer based on their history rather than a synthetic whiteboard test sug_kimhffx13kednhp 2021-07-12T18:51:59Z 2023-03-03T12:37:29Z sug_n2nnucjlvegpr75 2021-07-12T18:51:40Z 2023-03-03T12:37:29Z Allow code comments to have formatted code highlighting sug_y4mbpz8hkc7wrem 2021-07-12T18:50:41Z 2023-03-03T12:37:29Z 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 full-blown PR review tool that could track what code was previously viewed and only show authentically new work authored since last pull request review. sug_jbvhqyr71zdhj7i 2021-07-12T18:49:08Z 2023-03-03T12:37:29Z Allow customer access to a REST API to get the data from GitClear reports progamatically sug_jph6lvav6eo8gt9 2021-07-12T18:47:17Z 2023-03-03T12:37:29Z Add dark mode to all GitClear reports (not just the historical report and CAB report)