Merge branch 'main' into claude/add-grouping-sorting-options

zkoppert · web-flow · commit 36170c70abc4 · 2026-03-04T17:21:58.000-08:00
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -1 +1 @@
-* @github/ospo-github-actions
+* @zkoppert @jmeridth
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
@@ -2,7 +2,7 @@ blank_issues_enabled: false
 
 contact_links:
   - name: Ask a question
-    url: https://github.com/github/issue-metrics/discussions/new
+    url: https://github.com/github-community-projects/issue-metrics/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
diff --git a/.github/pull_request_template.md b/.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`
diff --git a/.github/workflows/contributor_report.yaml b/.github/workflows/contributor_report.yaml
@@ -27,12 +27,12 @@ jobs:
           echo "END_DATE=$end_date" >> "$GITHUB_ENV"
 
       - name: Run contributor action
-        uses: github-community-projects/contributors@0d5adc3833e89ee1f4145744f5d69313cf5ea238 # v1.7.8
+        uses: github-community-projects/contributors@aff93cf32786e5eb578185bdeb52b96f341ba79b # v2.0.2
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           START_DATE: ${{ env.START_DATE }}
           END_DATE: ${{ env.END_DATE }}
-          REPOSITORY: github/issue-metrics
+          REPOSITORY: github-community-projects/issue-metrics
           SPONSOR_INFO: "true"
 
       - name: Create issue
diff --git a/CONTRIBUTING.md b/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/issue-metrics/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/issue-metrics/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/issue-metrics/issues/new).
+- Open an [Issue](https://github.com/github-community-projects/issue-metrics/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/issue-metrics/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/issue-metrics/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/issue-metrics/issues/new?template=bug_report.yml).
+Please submit a bug report using our [GitHub Issues template](https://github.com/github-community-projects/issue-metrics/issues/new?template=bug_report.yml).
 
 ## Suggesting Enhancements
 
@@ -69,14 +69,14 @@ This section guides you through submitting an enhancement suggestion for issue-m
 
 - 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/issue-metrics/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/issue-metrics/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/issue-metrics/issues/new?template=feature_request.yml).
+Please submit an enhancement suggestion using our [GitHub Issues template](https://github.com/github-community-projects/issue-metrics/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/issue-metrics/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/issue-metrics/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.
diff --git a/Dockerfile b/Dockerfile
@@ -7,9 +7,9 @@ LABEL com.github.actions.name="issue-metrics" \
     com.github.actions.icon="check-square" \
     com.github.actions.color="white" \
     maintainer="@zkoppert" \
-    org.opencontainers.image.url="https://github.com/github/issue-metrics" \
-    org.opencontainers.image.source="https://github.com/github/issue-metrics" \
-    org.opencontainers.image.documentation="https://github.com/github/issue-metrics" \
+    org.opencontainers.image.url="https://github.com/github-community-projects/issue-metrics" \
+    org.opencontainers.image.source="https://github.com/github-community-projects/issue-metrics" \
+    org.opencontainers.image.documentation="https://github.com/github-community-projects/issue-metrics" \
     org.opencontainers.image.vendor="GitHub" \
     org.opencontainers.image.description="Gather metrics on issues/prs/discussions such as time to first response, count of issues opened, closed, etc."
 
diff --git a/README.md b/README.md
@@ -1,9 +1,12 @@
 # Issue Metrics Action
 
-[![CodeQL](https://github.com/github/issue-metrics/actions/workflows/github-code-scanning/codeql/badge.svg)](https://github.com/github/issue-metrics/actions/workflows/github-code-scanning/codeql)
-[![Docker Image CI](https://github.com/github/issue-metrics/actions/workflows/docker-image.yml/badge.svg)](https://github.com/github/issue-metrics/actions/workflows/docker-image.yml)
-[![Python package](https://github.com/github/issue-metrics/actions/workflows/python-package.yml/badge.svg)](https://github.com/github/issue-metrics/actions/workflows/python-package.yml)
-[![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/github/issue-metrics/badge)](https://scorecard.dev/viewer/?uri=github.com/github/issue-metrics)
+> [!IMPORTANT]
+> This repository has been transferred from `github/issue-metrics` to `github-community-projects/issue-metrics`. Please update any references to the old repository location.
+
+[![CodeQL](https://github.com/github-community-projects/issue-metrics/actions/workflows/github-code-scanning/codeql/badge.svg)](https://github.com/github-community-projects/issue-metrics/actions/workflows/github-code-scanning/codeql)
+[![Docker Image CI](https://github.com/github-community-projects/issue-metrics/actions/workflows/docker-image.yml/badge.svg)](https://github.com/github-community-projects/issue-metrics/actions/workflows/docker-image.yml)
+[![Python package](https://github.com/github-community-projects/issue-metrics/actions/workflows/python-package.yml/badge.svg)](https://github.com/github-community-projects/issue-metrics/actions/workflows/python-package.yml)
+[![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/github-community-projects/issue-metrics/badge)](https://scorecard.dev/viewer/?uri=github.com/github-community-projects/issue-metrics)
 [![OpenSSF Best Practices](https://www.bestpractices.dev/projects/9501/badge)](https://www.bestpractices.dev/projects/9501)
 
 This is a GitHub Action that searches for issues/pull requests/discussions in a repository, measures several metrics, and generates a report in form of a GitHub issue.
@@ -74,7 +77,7 @@ jobs:
           echo "last_month=$first_day..$last_day" >> "$GITHUB_ENV"
 
       - name: Run issue-metrics tool
-        uses: github/issue-metrics@v3
+        uses: github-community-projects/issue-metrics@v4
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           SEARCH_QUERY: 'repo:owner/repo is:issue created:${{ env.last_month }} -reason:"not planned"'
@@ -96,7 +99,7 @@ jobs:
 
 ## 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/issue-metrics/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/issue-metrics/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
 
diff --git a/action.yml b/action.yml
@@ -4,7 +4,7 @@ author: "github"
 description: "A GitHub Action to report out issue metrics"
 runs:
   using: "docker"
-  image: "docker://ghcr.io/github/issue_metrics:v3"
+  image: "docker://ghcr.io/github-community-projects/issue_metrics:v4"
 branding:
   icon: "check-square"
   color: "white"
diff --git a/docs/assign-team-instead-of-individual.md b/docs/assign-team-instead-of-individual.md
@@ -46,7 +46,7 @@ jobs:
         echo "last_month=$first_day..$last_day" >> "$GITHUB_ENV"
 
     - name: Run issue-metrics tool
-      uses: github/issue-metrics@v3
+      uses: github-community-projects/issue-metrics@v4
       env:
         GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         SEARCH_QUERY: 'repo:owner/repo is:issue created:${{ env.last_month }} -reason:"not planned"'
diff --git a/docs/authenticating-with-github-app-installation.md b/docs/authenticating-with-github-app-installation.md
@@ -38,7 +38,7 @@ jobs:
         echo "last_month=$first_day..$last_day" >> "$GITHUB_ENV"
 
     - name: Run issue-metrics tool
-      uses: github/issue-metrics@v3
+      uses: github-community-projects/issue-metrics@v4
       env:
         GH_APP_ID: ${{ secrets.GH_APP_ID }}
         GH_APP_INSTALLATION_ID: ${{ secrets.GH_APP_INSTALLATION_ID }}
diff --git a/docs/example-using-json-instead-markdown-output.md b/docs/example-using-json-instead-markdown-output.md
@@ -23,7 +23,7 @@ jobs:
     steps:
       - name: Run issue-metrics tool
         id: issue-metrics
-        uses: github/issue-metrics@v3
+        uses: github-community-projects/issue-metrics@v4
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           SEARCH_QUERY: 'repo:owner/repo is:issue created:2023-05-01..2023-05-31 -reason:"not planned"'
diff --git a/docs/example-workflows.md b/docs/example-workflows.md
@@ -37,7 +37,7 @@ jobs:
           echo "last_month=$first_day..$last_day" >> "$GITHUB_ENV"
 
       - name: Run issue-metrics tool
-        uses: github/issue-metrics@v3
+        uses: github-community-projects/issue-metrics@v4
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           SEARCH_QUERY: 'repo:owner/repo is:issue created:${{ env.last_month }} -reason:"not planned"'
@@ -73,7 +73,7 @@ jobs:
 
     steps:
       - name: Run issue-metrics tool
-        uses: github/issue-metrics@v3
+        uses: github-community-projects/issue-metrics@v4
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           SEARCH_QUERY: 'repo:owner/repo is:issue created:2023-05-01..2023-05-31 -reason:"not planned"'
@@ -122,7 +122,7 @@ jobs:
           echo "last_month=$first_day..$last_day" >> "$GITHUB_ENV"
 
       - name: Get issue metrics
-        uses: github/issue-metrics@v3
+        uses: github-community-projects/issue-metrics@v4
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           SEARCH_QUERY: 'repo:owner/repo1 repo:owner/repo2 is:issue created:${{ env.last_month }} -reason:"not planned"'
diff --git a/docs/measure-time.md b/docs/measure-time.md
@@ -2,7 +2,7 @@
 
 **Note**: The discussions API currently doesn't support the `LabeledEvent` so this action cannot measure the time spent in a label for discussions.
 
-Sometimes it is helpful to know how long an issue or pull request spent in a particular label. This action can be configured to measure the time spent in a label. This is different from only wanting to measure issues with a specific label. If that is what you want, see the section on [configuring your search query](https://github.com/github/issue-metrics/blob/main/README.md#search_query-issues-or-pull-requests-open-or-closed).
+Sometimes it is helpful to know how long an issue or pull request spent in a particular label. This action can be configured to measure the time spent in a label. This is different from only wanting to measure issues with a specific label. If that is what you want, see the section on [configuring your search query](https://github.com/github-community-projects/issue-metrics/blob/main/README.md#search_query-issues-or-pull-requests-open-or-closed).
 
 Here is an example workflow that does this:
 
@@ -24,7 +24,7 @@ jobs:
 
     steps:
       - name: Run issue-metrics tool
-        uses: github/issue-metrics@v3
+        uses: github-community-projects/issue-metrics@v4
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           LABELS_TO_MEASURE: "waiting-for-manager-approval,waiting-for-security-review"
diff --git a/docs/search-query.md b/docs/search-query.md
@@ -48,7 +48,7 @@ name: Monthly issue metrics
 on:
   workflow_dispatch:
   schedule:
-    - cron: '3 2 1 * *'
+    - cron: "3 2 1 * *"
 
 permissions:
   contents: read
@@ -59,34 +59,33 @@ jobs:
     runs-on: ubuntu-latest
     permissions:
       issues: write
-        pull-requests: read
+      pull-requests: read
 
     steps:
-
-    - name: Run issue-metrics tool for issues and prs opened in May 2023
-      uses: github/issue-metrics@v3
-      env:
-        GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        SEARCH_QUERY: 'repo:owner/repo created:2023-05-01..2023-05-31 -reason:"not planned"'
-
-    - name: Create issue for opened issues and prs
-      uses: peter-evans/create-issue-from-file@v4
-      with:
-        title: Monthly issue metrics report for opened issues and prs
-        token: ${{ secrets.GITHUB_TOKEN }}
-        content-filepath: ./issue_metrics.md
-        assignees: <YOUR_GITHUB_HANDLE_HERE>
-
-    - name: Run issue-metrics tool for issues and prs closed in May 2023
-      uses: github/issue-metrics@v3
-      env:
-        GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        SEARCH_QUERY: 'repo:owner/repo closed:2023-05-01..2023-05-31 -reason:"not planned"'
-
-    - name: Create issue for closed issues and prs
-      uses: peter-evans/create-issue-from-file@v4
-      with:
-        title: Monthly issue metrics report for closed issues and prs
-        content-filepath: ./issue_metrics.md
+      - name: Run issue-metrics tool for issues and prs opened in May 2023
+        uses: github-community-projects/issue-metrics@v4
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          SEARCH_QUERY: 'repo:owner/repo created:2023-05-01..2023-05-31 -reason:"not planned"'
+
+      - name: Create issue for opened issues and prs
+        uses: peter-evans/create-issue-from-file@v4
+        with:
+          title: Monthly issue metrics report for opened issues and prs
+          token: ${{ secrets.GITHUB_TOKEN }}
+          content-filepath: ./issue_metrics.md
+          assignees: <YOUR_GITHUB_HANDLE_HERE>
+
+      - name: Run issue-metrics tool for issues and prs closed in May 2023
+        uses: github-community-projects/issue-metrics@v4
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          SEARCH_QUERY: 'repo:owner/repo closed:2023-05-01..2023-05-31 -reason:"not planned"'
+
+      - name: Create issue for closed issues and prs
+        uses: peter-evans/create-issue-from-file@v4
+        with:
+          title: Monthly issue metrics report for closed issues and prs
+          content-filepath: ./issue_metrics.md
         assignees: <YOUR_GITHUB_HANDLE_HERE>
 ```
diff --git a/docs/verify-token-access-to-repository.md b/docs/verify-token-access-to-repository.md
@@ -4,7 +4,7 @@ GitHub PAT token access can be confusing. Here's a quick way to test if the toke
 
 **Remove this snippet after you've verified your token.**
 
-- Make sure you follow the token setup instructions [in the `README.md`](https://github.com/github/issue-metrics/tree/main?tab=readme-ov-file#use-as-a-github-action) first.
+- Make sure you follow the token setup instructions [in the `README.md`](https://github.com/github-community-projects/issue-metrics/tree/main?tab=readme-ov-file#use-as-a-github-action) first.
 
 - Replace `{owner/repo}` with your own repository information.
 
@@ -58,7 +58,7 @@ jobs:
           echo "last_month=$first_day..$last_day" >> "$GITHUB_ENV"
 
       - name: Run issue-metrics tool
-        uses: github/issue-metrics@v3
+        uses: github-community-projects/issue-metrics@v4
         env:
           GH_TOKEN: ${{ secrets.GH_TOKEN }}
           SEARCH_QUERY: "repo:{owner/repo} is:issue created:${{ env.last_month }}"
diff --git a/issue_metrics.py b/issue_metrics.py
@@ -220,7 +220,7 @@ def evaluate_markdown_file_size(output_file: str) -> None:
             f"Issue metrics markdown file is too large for GitHub issue body and has been \
 split into multiple files. ie. {output_file_name}, {file_name_without_extension}_1.md, etc. \
 The full file is saved as {file_name_without_extension}_full.md\n\
-See https://github.com/github/issue-metrics/blob/main/docs/dealing-with-large-issue-metrics.md"
+See https://github.com/github-community-projects/issue-metrics/blob/main/docs/dealing-with-large-issue-metrics.md"
         )
 
 
diff --git a/markdown_writer.py b/markdown_writer.py
@@ -259,7 +259,7 @@ def write_to_markdown(
         if not issues_with_metrics or len(issues_with_metrics) == 0:
             file.write("no issues found for the given search criteria\n\n")
             file.write("\n_This report was generated with the \
-[Issue Metrics Action](https://github.com/github/issue-metrics)_\n")
+[Issue Metrics Action](https://github.com/github-community-projects/issue-metrics)_\n")
             if search_query:
                 file.write(f"Search query used to find these items: `{search_query}`\n")
             return
@@ -364,7 +364,7 @@ def write_to_markdown(
                     file.write("\n")
                 file.write("\n")
         file.write("_This report was generated with the \
-[Issue Metrics Action](https://github.com/github/issue-metrics)_\n")
+[Issue Metrics Action](https://github.com/github-community-projects/issue-metrics)_\n")
         if search_query:
             file.write(f"Search query used to find these items: `{search_query}`\n")
 
diff --git a/test_issue_metrics.py b/test_issue_metrics.py
diff --git a/test_markdown_writer.py b/test_markdown_writer.py

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-* @github/ospo-github-actions`
	`1`	`+* @zkoppert @jmeridth`