bazel-contrib / bazel-contrib/rules_go

Report Nogo errors on only changed files.

Open
#4,328 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
1.5k
Forks
762
Avg merge
1d 11h
Merged PRs (30d)
12

Description

Hi,

Recently i was trying to get Nogo integrated with our existing Repo. One major integration hurdle I faced was,
When running nogo enabled, the bazel build fails on existing linter issues, even on files that the developer has not touched.

Given we have a large repo and with many services, we wanted to throw lint errors only on changed files.
I made some hacky patch to lint and report issues on only files the author has touched to overcome this.
So wanted to understand if there's anything on the roadmap to lint only the changes?

Contributor guide

Open the contributing guide

Research direction

Start by reviewing how Nogo is integrated into the Bazel build and how lint errors are currently reported for existing repositories. Done means establishing a supported way to report lint errors only for files changed by the developer.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.