-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add weekly workflow for github issues/pr metrics #29444
Changes from 3 commits
e770d03
e12bee9
fe9da9a
82eea8a
7630192
5d334a6
638d356
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,58 @@ | ||
name: Weekly repo metrics | ||
on: | ||
workflow_dispatch: | ||
schedule: | ||
- cron: '0 9 * * MON' | ||
|
||
permissions: | ||
issues: write | ||
pull-requests: read | ||
|
||
jobs: | ||
build: | ||
# this workflow will always fail in forks; bail if this isn't running in the upstream | ||
if: github.repository == 'aws/aws-cdk' | ||
name: metrics | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- name: Get dates for last week | ||
shell: bash | ||
run: | | ||
# Calculate the previous Monday's date | ||
PREVIOUS_MONDAY=$(date -d "last monday" "+%Y-%m-%d") | ||
|
||
# Calculate the current Sunday's date | ||
CURRENT_SUNDAY=$(date -d "next Sunday" "+%Y-%m-%d") | ||
|
||
# Set an environment variable with the date range | ||
echo "$PREVIOUS_MONDAY..$CURRENT_SUNDAY" | ||
echo "last_week=$first_day..$last_day" >> "$GITHUB_ENV" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Seems the variable needs to be updated with previous monday and current sunday There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch! |
||
|
||
- name: Report on issues | ||
uses: github/issue-metrics@v2 | ||
env: | ||
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
SEARCH_QUERY: 'repo:aws/aws-cdk is:issue created:${{ env.last_week }} -reason:"not planned"' | ||
|
||
- name: Create report for issues | ||
uses: peter-evans/create-issue-from-file@v5 | ||
with: | ||
title: Weekly issue metrics report | ||
token: ${{ secrets.GITHUB_TOKEN }} | ||
content-filepath: ./issue_metrics.md | ||
assignees: paulhcsun | ||
|
||
- name: Report on PRs | ||
uses: github/issue-metrics@v2 | ||
env: | ||
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
SEARCH_QUERY: 'repo:aws/aws-cdk is:pr created:${{ env.last_week }} -is:draft' | ||
|
||
- name: Create report for PRs | ||
uses: peter-evans/create-issue-from-file@v5 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not a blocker. Would like to know is it normal and safe to use third party github actions for aws owned repos? As I can see this action is not from a peter-evans/create-issue-from-file@v5 -> https://github.com/marketplace/actions/create-issue-from-file Sample verified action: https://github.com/marketplace/actions/checkout |
||
with: | ||
title: Weekly PR metrics report | ||
token: ${{ secrets.GITHUB_TOKEN }} | ||
content-filepath: ./issue_metrics.md | ||
assignees: paulhcsun |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QQ: Just would like to know if "next sunday" provides the current sunday or the upcoming sunday? Since the script runs every monday, does this gives the current sunday? We could also get the current sunday may be using "yesterday"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point as this would be run every monday, I'll update the naming.