You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are there strong opinions on what Awesome Go contributions should require going forward? I'm happy to clean up the documentation and submit a PR if the community can come to a decision on a replacement.
Go Report Card itself points to golangci-lint for linting and formatting. I'd also throw in a vote for something like meeting the baseline requirements in the OpenSSF Best Practices project (as shown on oapi-codegen's README, for example), though it is a bit more manual than Go Report Card.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
It looks like Go Report Card has been sunset without a clear alternative. The contributing guide still mentions Go Report Card requirements in the PR "Quick Checklist" section: https://github.com/avelino/awesome-go/blob/main/CONTRIBUTING.md?plain=1#L39
Are there strong opinions on what Awesome Go contributions should require going forward? I'm happy to clean up the documentation and submit a PR if the community can come to a decision on a replacement.
Go Report Card itself points to golangci-lint for linting and formatting. I'd also throw in a vote for something like meeting the baseline requirements in the OpenSSF Best Practices project (as shown on oapi-codegen's README, for example), though it is a bit more manual than Go Report Card.
P.S. Go Report Card, you will be missed!
All reactions