Suggested Changes on MR From Static Analysis

Problem to solve

Right now Rubocop will complain about my MR after running the pipeline and often the complaints can be auto fixed with rubocop -a. I would much rather if Rubocop commented on my issue and said "hey click here to view and merge my suggested changes into your MR". This would save me time checking out the branch running the auto correct and then pushing again and I can stay within the UI. A reviewer/maintainer could easily also press this on your behalf to save turnaround time to merge substantially.

Further details

(Include use cases, benefits, and/or goals)

Proposal

I imagine this could easily be implemented using bots that check your MR for failing static analysis and create another MR into your branch and comment this link on to your MR. This is probably a good first start but we may want to make this easy to set up using GitLab's UI rather than having to run your bot yourself. I imagine we could do even better with something like Github suggested changes because now we'd be able to have the static analysis improvements there as comments to simply click apply without going of to a separate MR.

What does success look like, and how can we measure that?

(If no way to measure success, link to an issue that will implement a way to measure this)

Links / references

Edited Nov 14, 2018 by Dylan Griffith (ex GitLab)
Assignee Loading
Time tracking Loading