Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove github.com/olebedev/config #1

Closed
wants to merge 1 commit into from
Closed

Conversation

griggsca91
Copy link
Owner

Repo - https://github.com/olebedev/config

  • The project has not made an official release within the last year and has open issues. - It has been 2 years since an update to the repo
  • The project is not responding to bug reports issued within 6 months of submission.
  • The project is not meeting quality standards as indicated by the Go Report Card or Code Coverage tests.
  • The quality standard links have been removed from the documentation.
  • The project is no longer open-sourced.
  • The project is incompatible with any Go version issued within the last year (there is hopefully an open PR about this at the project).

Related issue: avelino#5136

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

  • The repo documentation has a pkg.go.dev link.
  • The repo documentation has a coverage service link.
  • The repo documentation has a goreportcard link.
  • The repo has a version-numbered release and a go.mod file.
  • The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
  • Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

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

Pull Request content

  • The package has been added to the list in alphabetical order.
  • The package has an appropriate description with correct grammar.
  • As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

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 that they also 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! 😎

Repo - https://github.com/olebedev/config

- [x] The project has not made an official release within the last year and has open issues.
    - It has been 2 years since an update to the repo
- [x] The project is not responding to bug reports issued within 6 months of submission.
   - https://github.com/olebedev/config/issues?q=is%3Aissue+is%3Aclosed last closed issue was in 2018
- [ ] The project is not meeting quality standards as indicated by the Go Report Card or Code Coverage tests.
- [ ] The quality standard links have been removed from the documentation.
- [ ] The project is no longer open-sourced.
- [ ] The project is incompatible with any Go version issued within the last year (there is hopefully an open PR about this at the project).


Related issue: avelino#5136
@griggsca91 griggsca91 closed this Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant