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
The repo has a go.mod file and at least one SemVer release (vX.Y.Z).
The repo has an open source license.
The repo documentation has a pkg.go.dev link.
The repo documentation has a goreportcard link (grade A- or better).
The repo documentation has a coverage service link.
These are recommended and reported as warnings:
The repo has a continuous integration process (GitHub Actions, etc.).
CI runs tests that must pass before merging.
Pull Request content
These are validated automatically by CI:
This PR adds/removes/changes only one package.
The package has been added in alphabetical order.
The link text is the exact project name.
The description is clear, concise, non-promotional, and ends with a period.
The link in README.md matches the forge link above.
Category quality
Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure they still meet the Quality Standards.
The packages around my addition still meet the Quality Standards.
I removed the following packages around my addition: (none - verified existing packages meet standards)
How to fix: No SemVer release tag (e.g. v1.0.0) found.
Create a tagged release:
git tag v1.0.0
git push origin v1.0.0
Or create a release via GitHub's UI at https://github.com/cheikh2shift/godex/releases/new.
❌ pkg.go.dev: unreachable How to fix: The pkg.go.dev page could not be reached.
Ensure your module path in go.mod matches the URL. After pushing a tagged release, pkg.go.dev indexes the module automatically — this can take a few minutes. You can trigger it manually by visiting https://pkg.go.dev/your-module-path.
✅ Go Report Card: OK (grade unknown)
Additional checks
⚠️License: no open source license detected
How to fix: Add a LICENSE file to your repository root.
Choose one at https://choosealicense.com — common choices for Go projects: MIT, Apache-2.0, BSD-3-Clause. ⚠️Maturity: repo appears to have less than 5 months of history How to fix: Your repository needs at least 5 months of history since the first commit.
Please resubmit after the repository meets this requirement.
✅ CI/CD: GitHub Actions workflows detected
✅ README: present ⚠️Coverage: missing from PR body How to fix: Add a coverage service link to your PR description:
Popular options: [Codecov](https://codecov.io), [Coveralls](https://coveralls.io). Integrate one with your CI to track coverage automatically.
---
> **Action needed:** one or more required checks failed. Please update your PR body with the missing links and ensure the repository meets the [quality standards](https://github.com/avelino/awesome-go/blob/main/CONTRIBUTING.md#quality-standards).
_These checks are automated and do not replace maintainer review. See [CONTRIBUTING.md](https://github.com/avelino/awesome-go/blob/main/CONTRIBUTING.md) for full guidelines._
---
## PR Diff Validation
### Content checks
✅ **Files changed**: only README.md
✅ **Single item**: one package added
✅ **Link consistency**: README link matches forge link in PR body
✅ **Link text**: matches repository name
✅ **Description**: ends with punctuation
✅ **Description tone**: no promotional language detected
✅ **Category size**: Artificial Intelligence has 9 items
_Automated diff validation — does not replace maintainer review._
<!-- Sticky Pull Request Commentpr-quality-check -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Required links
Provide the links below. Our CI will automatically validate them.
Pre-submission checklist
Repository requirements
These are validated automatically by CI:
go.modfile and at least one SemVer release (vX.Y.Z).These are recommended and reported as warnings:
Pull Request content
These are validated automatically by CI:
Category quality
Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure they still meet the Quality Standards.