chore: update all references for repo transfer to github-community-projects#337
Merged
chore: update all references for repo transfer to github-community-projects#337
Conversation
zkoppert
approved these changes
Feb 26, 2026
…ojects ## What Updated all remaining references from `github/cleanowners` to `github-community-projects/cleanowners` across documentation, workflows, Docker image metadata, action definition, and usage examples. Also bumped action and container image version references from v1 to v2. ## Why The repository has been transferred from `github` to `github-community-projects` and the previous commit (c629df2) only covered CODEOWNERS and the PR template. This completes the migration so all URLs, image references, and usage examples point to the correct org and version. ## Notes - The action.yml docker image changed to `ghcr.io/github-community-projects/cleanowners:v2` — the v2 container image must be published at the new registry path before this ships or the action will break for consumers - README usage examples were bumped from `github/cleanowners@v1` to `github-community-projects/cleanowners@v2` — existing users following the README will adopt the new org and version simultaneously - The contributors_report.yaml workflow `REPOSITORY` env var was updated; if this workflow runs before the GitHub API recognizes the new org path, it will fail - OpenSSF Scorecard badge URL was updated; the scorecard service may need time to re-index under the new org Signed-off-by: jmeridth <jmeridth@gmail.com>
jmeridth
force-pushed
the
jm_codeowners
branch
from
c629df2 to
b7de453
Compare
jmeridth
changed the title
## What Removed the deprecated `suggestion-mode` option from the pylint config. ## Why The `suggestion-mode` option was removed in newer versions of pylint, causing an `E0015: Unrecognized option` error that fails the super-linter CI job. ## Notes - These errors were hidden until super-linter upgraded its bundled pylint version - Saw these errors [here](https://github.com/github-community-projects/contributors/actions/runs/22372943481/job/64756293990?pr=394#step:5:488) which made me check the version of python-lint in this repo and the config. Same issue here. - `suggestion-mode` was [removed in 4.0 of pylint](https://pylint.readthedocs.io/en/latest/whatsnew/4/4.0/index.html) Signed-off-by: Jason Meridth <jmeridth@gmail.com>
Signed-off-by: jmeridth <jmeridth@gmail.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Updated all remaining references from
github/cleanownerstogithub-community-projects/cleanownersacross documentation, workflows,Docker image metadata, action definition, and usage examples. Also bumped
action and container image version references from v1 to v2.
Why
The repository has been transferred from
githubtogithub-community-projectsand the previous commit (c629df2) only coveredCODEOWNERS and the PR template. This completes the migration so all URLs,
image references, and usage examples point to the correct org and version.
Notes
ghcr.io/github-community-projects/cleanowners:v2— the v2 container image must be published at the new registry path before this ships or the action will break for consumersgithub/cleanowners@v1togithub-community-projects/cleanowners@v2— existing users following the README will adopt the new org and version simultaneouslyREPOSITORYenv var was updated; if this workflow runs before the GitHub API recognizes the new org path, it will failPull Request
Proposed Changes
Readiness Checklist
Author/Contributor
make lintand fix any issues that you have introducedmake testand ensure you have test coverage for the lines you are introducing