Skip to content

Add open-code-review to Code Analysis - #6531

Open
lizhengfeng101 wants to merge 1 commit into
avelino:mainfrom
lizhengfeng101:add-open-code-review
Open

Add open-code-review to Code Analysis#6531
lizhengfeng101 wants to merge 1 commit into
avelino:mainfrom
lizhengfeng101:add-open-code-review

Conversation

@lizhengfeng101

Copy link
Copy Markdown

Required links

Pre-submission checklist

Repository requirements

  • The repo has a go.mod file and at least one SemVer release (v1.8.0).
  • The repo has an open source license (Apache-2.0).
  • The repo documentation has a pkg.go.dev link.
  • The repo documentation has a goreportcard link (A+).
  • The repo documentation has a coverage service link.
  • The repo has a continuous integration process (GitHub Actions).
  • CI runs tests that must pass before merging.

Pull Request content

  • This PR adds only one package.
  • The package has been added in alphabetical order (between lint and php-parser).
  • The link text is the exact project name (open-code-review).
  • The description is clear, concise, non-promotional, and ends with a period.
  • The link in README.md matches the forge link above.

Category quality

  • The packages around my addition still meet the Quality Standards.

Note on repository age

The GitHub repository was created in May 2026 (< 5 months ago). However, this project originated as Alibaba Group's internal official AI code review tool and has been running in production for over two years, serving tens of thousands of developers and identifying millions of code defects internally. It was recently open-sourced after thorough validation at massive scale. We believe the project's maturity, quality, and community traction (15k+ stars in ~2 months) demonstrate it meets the spirit of the 5-month requirement, even though the public repository is newer.

Thanks for considering! 🙏

Add alibaba/open-code-review — an AI-powered code review CLI tool.
@github-actions

Copy link
Copy Markdown

Automated Quality Checks

Required checks

Repo: accessible, has go.mod and SemVer release
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: Apache-2.0
⚠️ 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:

Coverage: https://app.codecov.io/gh/your-org/your-project

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**: Code Analysis has 33 items


_Automated diff validation — does not replace maintainer review._
<!-- Sticky Pull Request Commentpr-quality-check -->

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant