747c5ee2b1
See https://pkg.go.dev/golang.org/x/tools/gopls/internal/analysis/modernize for details. This ran into a few issues (arguably bugs in the modernize tool), which I will fix in the next commit, so that we have transparency what was done automatically. Beyond those hiccups, I believe all the changes applied are legitimate. Even where there might be no tangible direct gain, I would argue it's still better to use the "modern" way to avoid micro discussions in tiny style PRs later. Signed-off-by: beorn7 <beorn@grafana.com> |
||
|---|---|---|
| .. | ||
| io/prometheus | ||
| rwcommon | ||
| README.md | ||
| buf.gen.yaml | ||
| buf.lock | ||
| buf.yaml | ||
| codec.go | ||
| custom.go | ||
| remote.pb.go | ||
| remote.proto | ||
| types.pb.go | ||
| types.proto | ||
README.md
The compiled protobufs are version controlled and you won't normally need to re-compile them when building Prometheus.
If however you have modified the defs and do need to re-compile, run
make proto from the parent dir.
In order for the script to run, you'll need protoc (version 3.15.8) in
your PATH.