From cc8377fc614de94fc055a2ffab7a2f65a077e3dd Mon Sep 17 00:00:00 2001 From: Junya Okabe Date: Wed, 18 Oct 2023 01:44:22 +0900 Subject: [PATCH 1/2] add: quick start section --- README.md | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) diff --git a/README.md b/README.md index b575844..af65ce3 100644 --- a/README.md +++ b/README.md @@ -22,6 +22,57 @@ Feel free to inquire about its usage by creating an issue in this repository. To find syntax for search queries, check out the [documentation on searching issues and pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests) or the [documentation on searching discussions](https://docs.github.com/en/search-github/searching-on-github/searching-discussions). +## Quick Start + +Create a workflow file (ie. `.github/workflows/issue-metrics.yml`) in your repository with the following contents: + +**Note**: `repo:owner/repo` is the repository you want to measure metrics on + +```yaml + +```yaml +name: Monthly issue metrics +on: + workflow_dispatch: + schedule: + - cron: '3 2 1 * *' + +permissions: + issues: write + pull-requests: read + +jobs: + build: + name: issue metrics + runs-on: ubuntu-latest + steps: + - name: Get dates for last month + shell: bash + run: | + # Calculate the first day of the previous month + first_day=$(date -d "last month" +%Y-%m-01) + + # Calculate the last day of the previous month + last_day=$(date -d "$first_day +1 month -1 day" +%Y-%m-%d) + + #Set an environment variable with the date range + echo "$first_day..$last_day" + echo "last_month=$first_day..$last_day" >> "$GITHUB_ENV" + + - name: Run issue-metrics tool + uses: github/issue-metrics@v2 + env: + GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} + SEARCH_QUERY: 'repo:owner/repo is:issue created:${{ env.last_month }} -reason:"not planned"' + + - name: Create issue + uses: peter-evans/create-issue-from-file@v4 + with: + title: Monthly issue metrics report + token: ${{ secrets.GITHUB_TOKEN }} + content-filepath: ./issue_metrics.md +``` + ## Example use cases - As a maintainer, I want to see metrics for issues and pull requests on the repository I maintain in order to ensure I am giving them the proper amount of attention. From 6ad90e8d1b9ad21dde7916535ef25129b5d35db4 Mon Sep 17 00:00:00 2001 From: Junya Okabe <86868255+Okabe-Junya@users.noreply.github.com> Date: Wed, 18 Oct 2023 23:00:02 +0900 Subject: [PATCH 2/2] update: subsection title Co-authored-by: Zack Koppert --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index af65ce3..5988bb8 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ Feel free to inquire about its usage by creating an issue in this repository. To find syntax for search queries, check out the [documentation on searching issues and pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests) or the [documentation on searching discussions](https://docs.github.com/en/search-github/searching-on-github/searching-discussions). -## Quick Start +## Getting Started Create a workflow file (ie. `.github/workflows/issue-metrics.yml`) in your repository with the following contents: