Skip to content

Adding Arcops - #6647

Open
Parthtiw710 wants to merge 1 commit into
avelino:mainfrom
Parthtiw710:main
Open

Parthtiw710 wants to merge 1 commit into
avelino:mainfrom
Parthtiw710:main

Conversation

@Parthtiw710

Copy link
Copy Markdown

Required links

Provide the links below. Our CI will automatically validate them.

  • Forge link (github.com, gitlab.com, etc):
  • pkg.go.dev:
  • goreportcard.com:
  • Coverage service link (codecov, coveralls, etc.):

Pre-submission checklist

Repository requirements

These are validated automatically by CI:

  • 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

Note: new categories require a minimum of 3 packages.

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.

Please delete one of the following lines:

  • The packages around my addition still meet the Quality Standards.
  • I removed the following packages around my addition: (please give a short reason for each removal)

Thanks for your PR, you're awesome! 😎

@github-actions

Copy link
Copy Markdown

Automated Quality Checks

Required checks

Repo link: missing from PR body

How to fix: Add the following to your PR description:

Forge link: https://github.com/your-org/your-project

❌ **pkg.go.dev**: missing from PR body
  > **How to fix:** Add the following to your PR description:
  > ```
pkg.go.dev: https://pkg.go.dev/github.com/your-org/your-project

Go Report Card: missing from PR body

How to fix: Add the following to your PR description:

goreportcard.com: https://goreportcard.com/report/github.com/your-org/your-project


### Additional checks

⚠️ **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, Coveralls. 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.

These checks are automated and do not replace maintainer review. See CONTRIBUTING.md for full guidelines.


PR Diff Validation

Content checks

Files changed: only README.md
Single item: one package added
Description: ends with punctuation
Description tone: no promotional language detected
Category size: All-in-one PAAS + BAAS Tools has only 1 item(s) (minimum 3 required)

How to fix: Categories must have at least 3 packages.
Either add more packages to this category in the same PR, or add your package to an existing category that already has 3+ items.

Warnings

⚠️ Link text: arcops differs from repo name Arcops_1.0

How to fix: The link text should be the exact project name.
If the project name really is arcops, this is fine. Otherwise change it to: - [Arcops_1.0](https://github.com/Parthtiw710/Arcops_1.0) - ...


Action needed: one or more content checks failed. Please review the contribution guidelines.

Automated diff validation — does not replace maintainer review.

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