---
# System prepended metadata

title: Help us clean up our Go repositories

---

# Help us clean up our Go repositories

The stewards team is in the process of [rolling out a new CI workflow across all of PL's Go repositories](https://github.com/protocol/.github/issues/41). We will finally have a consistent CI strategy across the entire company! The cool thing about this new setup is that we'll be able to update it in the future, e.g. to add support for a new Go version.

The workflow does the most basic checks:

* run all tests (with an without race detector), on Linux, Mac, Windows
* run gofmt, go vet and staticcheck

Problem: At the moment, every repository uses a different setup, so most repositories will fail at least one of the checks listed above. That's why we need your help to clean them up once (after that, CI will enforce these rules on every PR).

## Contribute

Pick repositories from [this spreadsheet](https://docs.google.com/spreadsheets/d/1Vwk-OUKXXNQkp4BkOoMndLylnJRW7a2c_mmvXu6jIj8/edit#gid=0). Either pick code that you're familiar with, otherwise pick a repository that has had a lot of commits in the last 6 months. With every repo:

* run `go test ./...` and `go test -race ./...`
* run `go vet ./...`
* run `staticcheck ./...`

and create one / multiple PRs to fix the errors. Then paste a link to the PR(s) in the comment column in the spreadsheet.