Bug 575501 - Gerrit plugin to add code warnings as comment and reformat (and apply cleanups)
Summary: Gerrit plugin to add code warnings as comment and reformat (and apply cleanups)
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.21   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-19 04:06 EDT by Carsten Hammer CLA
Modified: 2021-08-19 04:15 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Hammer CLA 2021-08-19 04:06:44 EDT
It would be nice if gerrit would be able to add comments to your gerrit either automatically or by explicit trigger button (like rebase) about each warning that you can see in Eclipse on your project.

Additionally there should be a reformat button that reformats code (updating the gerrit) according to the project settings. Really cool would be if it automatically warns you that code in gerrit would be changed as soon as you hit the formatting button. That points to either a misconfiguration of the project settings or outdated formatting of the code.

A third feature could be to add comments regarding application of possible quickfixes and provide a button to apply and update the gerrit.

For all of that one could think of a first step to get some statistics within gerrit about how many files in the gerrit have formatting issues, warnings and how many hits each of the cleanups has within the gerrit.

As a starting point the formatting feature could be implemented based on what we have since Bug 75333.

https://gerrit-review.googlesource.com/Documentation/dev-plugins.html#getting-started

https://gerrit.googlesource.com/plugins/examples/+/refs/heads/master

Not sure if there is a dedicated project for gerrit plugins within the eclipse universe.
So far Bug 565280 does not progress any longer. Maybe it is easier to justify effort if Eclipse itself is part of the solution like in this enhancement?

I think such a feature could be a "unique selling point" for Eclipse.