github-community-projects · zkoppert · Feb 28, 2026 · Feb 27, 2026 · Feb 27, 2026 · Feb 27, 2026
@@ -1 +1 @@
-* @github/ospo-github-actions
+* @zkoppert @jmeridth
@@ -2,7 +2,7 @@ blank_issues_enabled: false
 
 contact_links:
   - name: Ask a question
-    url: https://github.com/github/stale-repos/discussions/new
+    url: https://github.com/github-community-projects/stale-repos/discussions/new
     about: Ask a question or start a discussion
   - name: GitHub OSPO GitHub Action Overall Issue
     url: https://github.com/github/github-ospo/issues/new

@@ -20,8 +20,3 @@ examples: "feat: add new logger" or "fix: remove unused imports"
 - [ ] If documentation is needed for this change, has that been included in this pull request
 - [ ] run `make lint` and fix any issues that you have introduced
 - [ ] run `make test` and ensure you have test coverage for the lines you are introducing
-- [ ] If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from `@jeffrey-luszcz`
-
-### Reviewer
-
-- [ ] Label as either `fix`, `documentation`, `enhancement`, `infrastructure`, `maintenance` or `breaking`
@@ -23,7 +23,7 @@ jobs:
         with:
           persist-credentials: false
       - name: Run stale_repos tool
-        uses: docker://ghcr.io/github/stale_repos:v6
+        uses: docker://ghcr.io/github-community-projects/stale_repos:v7
         env:
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
           ORGANIZATION: github

@@ -19,11 +19,11 @@ All types of contributions are encouraged and valued. See the [Table of Contents
 
 ## I Have a Question
 
-Before you ask a question, it is best to search for existing [Issues](https://github.com/github/stale-repos/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.
+Before you ask a question, it is best to search for existing [Issues](https://github.com/github-community-projects/stale-repos/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.
 
 If you then still feel the need to ask a question and need clarification, we recommend the following:
 
-- Open an [Issue](https://github.com/github/stale-repos/issues/new).
+- Open an [Issue](https://github.com/github-community-projects/stale-repos/issues/new).
 - Provide as much context as you can about what you're running into.
 - Provide project and platform versions (Node.js, npm, etc), depending on what seems relevant.
 
@@ -45,7 +45,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 - Make sure that you are using the latest version.
 - 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)).
-- 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/stale-repos/issues).
+- 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/stale-repos/issues).
 - Collect information about the bug:
   - Stack trace (Traceback)
   - 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
 
 ### How Do I Submit a Good Bug Report?
 
-Please submit a bug report using our [GitHub Issues template](https://github.com/github/stale-repos/issues/new?template=bug_report.yml).
+Please submit a bug report using our [GitHub Issues template](https://github.com/github-community-projects/stale-repos/issues/new?template=bug_report.yml).
 
 ## Suggesting Enhancements
 
@@ -69,14 +69,14 @@ This section guides you through submitting an enhancement suggestion for stale_r
 
 - Make sure that you are using the latest version.
 - Read the documentation carefully and find out if the functionality is already covered, maybe by an individual configuration.
-- Perform a [search](https://github.com/github/stale-repos/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.
+- Perform a [search](https://github.com/github-community-projects/stale-repos/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.
 - 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.
 
 <!-- omit in toc -->
 
 ### How Do I Submit a Good Enhancement Suggestion?
 
-Please submit an enhancement suggestion using our [GitHub Issues template](https://github.com/github/stale-repos/issues/new?template=feature_request.yml).
+Please submit an enhancement suggestion using our [GitHub Issues template](https://github.com/github-community-projects/stale-repos/issues/new?template=feature_request.yml).
 
 ### Pull Request Standards
 
@@ -86,4 +86,4 @@ We are using [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.
 
 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.
 
-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/stale-repos/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.
+You can also manually initiate a release 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/stale-repos/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.
@@ -7,9 +7,9 @@ LABEL com.github.actions.name="stale-repos" \
     com.github.actions.icon="check-square" \
     com.github.actions.color="white" \
     maintainer="@zkoppert" \
-    org.opencontainers.image.url="https://github.com/github/stale-repos" \
-    org.opencontainers.image.source="https://github.com/github/stale-repos" \
-    org.opencontainers.image.documentation="https://github.com/github/stale-repos" \
+    org.opencontainers.image.url="https://github.com/github-community-projects/stale-repos" \
+    org.opencontainers.image.source="https://github.com/github-community-projects/stale-repos" \
+    org.opencontainers.image.documentation="https://github.com/github-community-projects/stale-repos" \
     org.opencontainers.image.vendor="GitHub" \
     org.opencontainers.image.description="Find stale repositories in a GitHub organization."
 

@@ -1,10 +1,20 @@
 # Stale Repos Action
 
-[![Lint Code Base](https://github.com/github/stale-repos/actions/workflows/linter.yaml/badge.svg)](https://github.com/github/stale-repos/actions/workflows/linter.yaml)
-[![CodeQL](https://github.com/github/stale-repos/actions/workflows/github-code-scanning/codeql/badge.svg)](https://github.com/github/stale-repos/actions/workflows/github-code-scanning/codeql)
-[![Docker Image CI](https://github.com/github/stale-repos/actions/workflows/docker-image.yml/badge.svg)](https://github.com/github/stale-repos/actions/workflows/docker-image.yml)
-[![Python CI](https://github.com/github/stale-repos/actions/workflows/python-package.yml/badge.svg)](https://github.com/github/stale-repos/actions/workflows/python-package.yml)
-[![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/github/stale-repos/badge)](https://scorecard.dev/viewer/?uri=github.com/github/stale-repos)
+> [!IMPORTANT]
+> This repository has moved from `github/stale-repos` to `github-community-projects/stale-repos`.
+> Please update your git remote:
+>
+> ```shell
+> git remote set-url origin git@github.com:github-community-projects/stale-repos.git
+> ```
+>
+> Note: replace `origin` with the name of your remote if it's different.
+
+[![Lint Code Base](https://github.com/github-community-projects/stale-repos/actions/workflows/linter.yaml/badge.svg)](https://github.com/github-community-projects/stale-repos/actions/workflows/linter.yaml)
+[![CodeQL](https://github.com/github-community-projects/stale-repos/actions/workflows/github-code-scanning/codeql/badge.svg)](https://github.com/github-community-projects/stale-repos/actions/workflows/github-code-scanning/codeql)
+[![Docker Image CI](https://github.com/github-community-projects/stale-repos/actions/workflows/docker-image.yml/badge.svg)](https://github.com/github-community-projects/stale-repos/actions/workflows/docker-image.yml)
+[![Python CI](https://github.com/github-community-projects/stale-repos/actions/workflows/python-package.yml/badge.svg)](https://github.com/github-community-projects/stale-repos/actions/workflows/python-package.yml)
+[![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/github-community-projects/stale-repos/badge)](https://scorecard.dev/viewer/?uri=github.com/github-community-projects/stale-repos)
 
 (Used by the `github` organization!)
 
@@ -20,7 +30,7 @@ If you are looking to identify stale pull requests and issues, check out [action
 
 ## Support
 
-If you need support using this project or have questions about it, please [open up an issue in this repository](https://github.com/github/stale-repos/issues).
+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/stale-repos/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.
 
@@ -98,7 +108,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Run stale_repos tool
-        uses: github/stale-repos@v6
+        uses: github-community-projects/stale-repos@v7
         env:
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
           ORGANIZATION: ${{ secrets.ORGANIZATION }}
@@ -147,7 +157,7 @@ jobs:
 
     steps:
       - name: Run stale_repos tool
-        uses: github/stale-repos@v6
+        uses: github-community-projects/stale-repos@v7
         env:
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
           ORGANIZATION: ${{ secrets.ORGANIZATION }}
@@ -196,7 +206,7 @@ jobs:
     steps:
       - name: Run stale_repos tool
         id: stale-repos
-        uses: github/stale-repos@v3
+        uses: github-community-projects/stale-repos@v7
         env:
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
           ORGANIZATION: ${{ secrets.ORGANIZATION }}
@@ -245,7 +255,7 @@ jobs:
         org: [org1, org2]
     steps:
       - name: "run stale-repos"
-        uses: github/stale-repos@v3
+        uses: github-community-projects/stale-repos@v7
         env:
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
           ORGANIZATION: ${{ matrix.org }}
@@ -275,7 +285,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Run stale_repos tool
-        uses: github/stale-repos@v6
+        uses: github-community-projects/stale-repos@v7
         env:
           GH_APP_ID: ${{ secrets.GH_APP_ID }}
           GH_APP_INSTALLATION_ID: ${{ secrets.GH_APP_INSTALLATION_ID }}

@@ -7,7 +7,7 @@ outputs:
     description: "Inactive Repos in the organization"
 runs:
   using: "docker"
-  image: "docker://ghcr.io/github/stale_repos:v6"
+  image: "docker://ghcr.io/github-community-projects/stale_repos:v7"
 branding:
   icon: "check-square"
   color: "white"
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		* @github/ospo-github-actions
		* @zkoppert @jmeridth