commit with obvious gofmt issue

[willnorris]

No description provided.

[willnorris]

@gmlewis well this one failed: https://github.com/google/go-github/runs/6220310903?check_suite_focus=true

weird.

[codecov]

Codecov Report

Merging #2348 (2941973) into master (ca149ad) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2348   +/-   ##
=======================================
  Coverage   98.05%   98.05%           
=======================================
  Files         119      119           
  Lines       10471    10471           
=======================================
  Hits        10267    10267           
  Misses        140      140           
  Partials       64       64           

Impacted Files	Coverage Δ
github/github.go	97.73% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ca149ad...2941973. Read the comment docs.

[willnorris]

This looks to be a problem with golangci-lint, or how we're using it. Running it manually at commit 51df464 (the last in #2333 before the gofmt fix) passes when it shouldn't. I'll keep digging.

[willnorris]

Ah, I think I found it.... it's because the example directory is its own go module. I don't think golangci-lint will descent into other modules. cd'ing into the examples directory and then running golangci-lint there correctly identifies the issue. So we'll need to change our actions workflow to manually run on examples and scrape and any other separate modules we have. Gotta run for now, but I can take a look at that later.