Merge pull request #116 from github-community-projects/update-org-name

fix: Update org name from github to github-community-projects

Author: zkoppert

.github/CODEOWNERS

@@ -1 +1 @@
-* @github/ospo-github-actions
+* @zkoppert @jmeridth

.github/ISSUE_TEMPLATE/config.yml

@@ -2,7 +2,7 @@ blank_issues_enabled: true
 
 contact_links:
   - name: Ask a question
-    url: https://github.com/github/measure-innersource/discussions/new
+    url: https://github.com/github-community-projects/measure-innersource/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

.github/pull_request_template.md

@@ -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`

.github/workflows/contributor_report.yaml

@@ -32,7 +32,7 @@ jobs:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           START_DATE: ${{ env.START_DATE }}
           END_DATE: ${{ env.END_DATE }}
-          REPOSITORY: github/measure-innersource
+          REPOSITORY: github-community-projects/measure-innersource
           SPONSOR_INFO: "true"
 
       - name: Create issue

CONTRIBUTING.md

@@ -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/measure-innersource/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/measure-innersource/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/measure-innersource/issues/new).
+- Open an [Issue](https://github.com/github-community-projects/measure-innersource/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/measure-innersource/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/measure-innersource/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/measure-innersource/issues/new?template=bug_report.yml).
+Please submit a bug report using our [GitHub Issues template](https://github.com/github-community-projects/measure-innersource/issues/new?template=bug_report.yml).
 
 ## Suggesting Enhancements
 
@@ -69,14 +69,14 @@ This section guides you through submitting an enhancement suggestion for measure
 
 - 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/measure-innersource/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/measure-innersource/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/measure-innersource/issues/new?template=feature_request.yml).
+Please submit an enhancement suggestion using our [GitHub Issues template](https://github.com/github-community-projects/measure-innersource/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/measure-innersource/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 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/measure-innersource/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.

Dockerfile

@@ -7,9 +7,9 @@ LABEL com.github.actions.name="measure-innersource" \
     com.github.actions.icon="bar-chart" \
     com.github.actions.color="white" \
     maintainer="@zkoppert" \
-    org.opencontainers.image.url="https://github.com/github/measure-innersource" \
-    org.opencontainers.image.source="https://github.com/github/measure-innersource" \
-    org.opencontainers.image.documentation="https://github.com/github/measure-innersource" \
+    org.opencontainers.image.url="https://github.com/github-community-projects/measure-innersource" \
+    org.opencontainers.image.source="https://github.com/github-community-projects/measure-innersource" \
+    org.opencontainers.image.documentation="https://github.com/github-community-projects/measure-innersource" \
     org.opencontainers.image.vendor="GitHub" \
     org.opencontainers.image.description="Measure and report on the InnerSource collaboration occurring in a given repository"
 

README.md

@@ -1,5 +1,15 @@
 # Measure InnerSource tool
 
+> [!IMPORTANT]
+> This repository has moved from `github/measure-innersource` to `github-community-projects/measure-innersource`.
+> Please update your git remote:
+>
+> ```shell
+> git remote set-url origin git@github.com:github-community-projects/measure-innersource.git
+> ```
+>
+> Note: replace `origin` with the name of your remote if it's different.
+
 This tool measures InnerSource collaboration in a given repository by analyzing issues, pull requests, and code contributions. It helps organizations track and improve their InnerSource adoption by quantifying the collaboration between different teams and departments.
 
 ## What is InnerSource?
@@ -358,7 +368,7 @@ Below is an example of the generated InnerSource report:
 
 ## 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/measure-innersource/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.
+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/measure-innersource/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.
 
 ### OSPO GitHub Actions as a Whole
 
@@ -393,7 +403,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Measure InnerSource
-        uses: github/measure-innersource@v1
+        uses: github-community-projects/measure-innersource@v2
         env:
           REPOSITORY: "owner/repo"
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
@@ -423,7 +433,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Measure InnerSource
-        uses: github/measure-innersource@v1
+        uses: github-community-projects/measure-innersource@v2
         env:
           REPOSITORY: "owner/repo"
           GH_APP_ID: ${{ secrets.APP_ID }}
@@ -454,7 +464,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Measure InnerSource
-        uses: github/measure-innersource@v1
+        uses: github-community-projects/measure-innersource@v2
         env:
           REPOSITORY: "internal-org/critical-service"
           GH_TOKEN: ${{ secrets.GHE_TOKEN }}
@@ -484,7 +494,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Measure InnerSource
-        uses: github/measure-innersource@v1
+        uses: github-community-projects/measure-innersource@v2
         env:
           REPOSITORY: "bigcorp/massive-monorepo"
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
@@ -521,7 +531,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Measure InnerSource for ${{ matrix.repository }}
-        uses: github/measure-innersource@v1
+        uses: github-community-projects/measure-innersource@v2
         env:
           REPOSITORY: ${{ matrix.repository }}
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
@@ -550,7 +560,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Measure InnerSource
-        uses: github/measure-innersource@v1
+        uses: github-community-projects/measure-innersource@v2
         env:
           REPOSITORY: "org/repository"
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
@@ -595,7 +605,7 @@ This action can be configured to authenticate with GitHub App Installation or Pe
 | `RATE_LIMIT_BYPASS` | False    | `false`                 | If set to `true`, the rate limit will be bypassed. This is useful if being run on an local GitHub server with rate limiting disabled.               |
 | `OUTPUT_FILE`       | False    | `innersource_report.md` | Output filename.                                                                                                                                    |
 | `REPORT_TITLE`      | False    | `"InnerSource Report"`  | Title to have on the report issue.                                                                                                                  |
-| `REPOSITORY`        | True     | `""`                    | The name of the repository you are trying to measure. Format `owner/repo` ie. `github/measure-innersource`                                          |
+| `REPOSITORY`        | True     | `""`                    | The name of the repository you are trying to measure. Format `owner/repo` ie. `github-community-projects/measure-innersource`                       |
 | `CHUNK_SIZE`        | False    | `100`                   | Number of items to process at once when fetching data. Increasing can improve performance but uses more memory. Minimum value is 10.                |
 | `OWNING_TEAM`       | False    | `""`                    | Comma-separated list of GitHub usernames that own the repository. Overrides the built-in team determination algorithm. Example: `alice,bob,charlie` |
 
@@ -826,7 +836,7 @@ The tool automatically splits large files, but you can:
 
 If you continue to experience issues:
 
-1. **Check Existing Issues**: Search the [GitHub Issues](https://github.com/github/measure-innersource/issues) for similar problems
+1. **Check Existing Issues**: Search the [GitHub Issues](https://github.com/github-community-projects/measure-innersource/issues) for similar problems
 2. **Create a New Issue**: Include:
    - Error messages (sanitized of sensitive information)
    - Configuration details (without secrets)

action.yml

@@ -4,7 +4,7 @@ author: "github"
 description: "A GitHub Action to measure and report how much innersource collaboration in a repo"
 runs:
   using: "docker"
-  image: "docker://ghcr.io/github/measure_innersource:v1"
+  image: "docker://ghcr.io/github-community-projects/measure_innersource:v2"
 branding:
   icon: "bar-chart"
   color: "white"