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
chore: update all references for repo transfer to github-community-projects (#337)
* chore: update all references for repo transfer to github-community-projects
## 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>
* fix: resolve pylint config errors breaking super-linter
## 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>
* fix: linting
Signed-off-by: jmeridth <jmeridth@gmail.com>
---------
Signed-off-by: jmeridth <jmeridth@gmail.com>
Signed-off-by: Jason Meridth <jmeridth@gmail.com>
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
-5Lines changed: 0 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,8 +20,3 @@ examples: "feat: add new logger" or "fix: remove unused imports"
20
20
-[ ] If documentation is needed for this change, has that been included in this pull request
21
21
-[ ] run `make lint` and fix any issues that you have introduced
22
22
-[ ] run `make test` and ensure you have test coverage for the lines you are introducing
23
-
-[ ] If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from `@jeffrey-luszcz`
24
-
25
-
### Reviewer
26
-
27
-
-[ ] Label as either `fix`, `documentation`, `enhancement`, `infrastructure`, `maintenance` or `breaking`
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,11 +19,11 @@ All types of contributions are encouraged and valued. See the [Table of Contents
19
19
20
20
## I Have a Question
21
21
22
-
Before you ask a question, it is best to search for existing [Issues](https://github.com/github/cleanowners/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue.
22
+
Before you ask a question, it is best to search for existing [Issues](https://github.com/github-community-projects/cleanowners/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue.
23
23
24
24
If you then still feel the need to ask a question and need clarification, we recommend the following:
25
25
26
-
- Open an [Issue](https://github.com/github/cleanowners/issues/new).
26
+
- Open an [Issue](https://github.com/github-community-projects/cleanowners/issues/new).
27
27
- Provide as much context as you can about what you're running into.
28
28
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
29
29
@@ -45,7 +45,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
45
45
46
46
- Make sure that you are using the latest version.
47
47
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the documentation. If you are looking for support, you might want to check [this section](#i-have-a-question)).
48
-
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/github/cleanowners/issues).
48
+
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/github-community-projects/cleanowners/issues).
49
49
- Collect information about the bug:
50
50
- Stack trace (Traceback)
51
51
- OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
@@ -57,7 +57,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
57
57
58
58
### How Do I Submit a Good Bug Report?
59
59
60
-
Please submit a bug report using our [GitHub Issues template](https://github.com/github/cleanowners/issues/new?template=bug_report.yml).
60
+
Please submit a bug report using our [GitHub Issues template](https://github.com/github-community-projects/cleanowners/issues/new?template=bug_report.yml).
61
61
62
62
## Suggesting Enhancements
63
63
@@ -69,14 +69,14 @@ This section guides you through submitting an enhancement suggestion for cleanow
69
69
70
70
- Make sure that you are using the latest version.
71
71
- Read the documentation carefully and find out if the functionality is already covered, maybe by an individual configuration.
72
-
- Perform a [search](https://github.com/github/cleanowners/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
72
+
- Perform a [search](https://github.com/github-community-projects/cleanowners/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
73
73
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature or to develop the feature yourself and contribute it to the project.
74
74
75
75
<!-- omit in toc -->
76
76
77
77
### How Do I Submit a Good Enhancement Suggestion?
78
78
79
-
Please submit an enhancement suggestion using our [GitHub Issues template](https://github.com/github/cleanowners/issues/new?template=feature_request.yml).
79
+
Please submit an enhancement suggestion using our [GitHub Issues template](https://github.com/github-community-projects/cleanowners/issues/new?template=feature_request.yml).
80
80
81
81
### Pull Request Standards
82
82
@@ -86,4 +86,4 @@ We are using [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.
86
86
87
87
Releases are automated if a pull request is labelled with our [semver related labels](.github/release-drafter.yml) or with the `vuln` or `release` labels.
88
88
89
-
You can also manually initiate a release you can do so through the GitHub Actions UI. If you have permissions to do so, you can navigate to the [Actions tab](https://github.com/github/cleanowners/actions/workflows/release.yml) and select the `Run workflow` button. This will allow you to select the branch to release from and the version to release.
89
+
You can also manually initiate a release you can do so through the GitHub Actions UI. If you have permissions to do so, you can navigate to the [Actions tab](https://github.com/github-community-projects/cleanowners/actions/workflows/release.yml) and select the `Run workflow` button. This will allow you to select the branch to release from and the version to release.
Cleanowners is a GitHub Action that is designed to help keep `CODEOWNERS` files current by removing users that are no longer a part of the organization. This is helpful for companies that are looking to remove outdated information in the `CODEOWNERS` file. This action can be paired with other `CODEOWNERS` related actions to suggest new owners or lint `CODEOWNERS` files to ensure accuracy.
6
6
@@ -10,7 +10,7 @@ This action was developed by the GitHub OSPO for our own use and developed in a
10
10
11
11
## Support
12
12
13
-
If you need support using this project or have questions about it, please [open up an issue in this repository](https://github.com/github/cleanowners/issues). Requests made directly to GitHub staff or support team will be redirected here to open an issue. GitHub SLA's and support/services contracts do not apply to this repository.
13
+
If you need support using this project or have questions about it, please [open up an issue in this repository](https://github.com/github-community-projects/cleanowners/issues). Requests made directly to GitHub staff or support team will be redirected here to open an issue. GitHub SLA's and support/services contracts do not apply to this repository.
14
14
15
15
### OSPO GitHub Actions as a Whole
16
16
@@ -52,14 +52,14 @@ This action can be configured to authenticate with GitHub App Installation or Pe
|`GH_ENTERPRISE_URL`| False | "" | The `GH_ENTERPRISE_URL` is used to connect to an enterprise server instance of GitHub. github.com users should not enter anything here. |
58
-
|`ORGANIZATION`| Required to have `ORGANIZATION` or `REPOSITORY`|| The name of the GitHub organization which you want this action to work from. ie. github.com/github would be `github`|
59
-
|`REPOSITORY`| Required to have `ORGANIZATION` or `REPOSITORY`|| The name of the repository and organization which you want this action to work from. ie. `github/cleanowners` or a comma separated list of multiple repositories `github/cleanowners,super-linter/super-linter`|
60
-
|`EXEMPT_REPOS`| False | "" | These repositories will be exempt from this action. ex: If my org is set to `github` then I might want to exempt a few of the repos but get the rest by setting `EXEMPT_REPOS` to `github/cleanowners,github/contributors`|
61
-
|`DRY_RUN`| False | False | If set to true, this action will not create any pull requests. It will only log the repositories that could have the `CODEOWNERS` file updated. This is useful for testing or discovering the scope of this issue in your organization. |
62
-
|`ISSUE_REPORT`| False | False | If set to true, this action will create an issue in the repository with the report on the repositories that had users removed from the `CODEOWNERS` file. |
|`GH_ENTERPRISE_URL`| False | "" | The `GH_ENTERPRISE_URL` is used to connect to an enterprise server instance of GitHub. github.com users should not enter anything here. |
58
+
|`ORGANIZATION`| Required to have `ORGANIZATION` or `REPOSITORY`|| The name of the GitHub organization which you want this action to work from. ie. github.com/github would be `github`|
59
+
|`REPOSITORY`| Required to have `ORGANIZATION` or `REPOSITORY`|| The name of the repository and organization which you want this action to work from. ie. `github-community-projects/cleanowners` or a comma separated list of multiple repositories `github-community-projects/cleanowners,super-linter/super-linter`|
60
+
|`EXEMPT_REPOS`| False | "" | These repositories will be exempt from this action. ex: If my org is set to `github` then I might want to exempt a few of the repos but get the rest by setting `EXEMPT_REPOS` to `github-community-projects/cleanowners,github/contributors`|
61
+
|`DRY_RUN`| False | False | If set to true, this action will not create any pull requests. It will only log the repositories that could have the `CODEOWNERS` file updated. This is useful for testing or discovering the scope of this issue in your organization. |
62
+
|`ISSUE_REPORT`| False | False | If set to true, this action will create an issue in the repository with the report on the repositories that had users removed from the `CODEOWNERS` file. |
0 commit comments