chore: add addedon field automation in prioritization board #33856
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #33856 +/- ##
=======================================
Coverage 82.35% 82.35%
=======================================
Files 120 120
Lines 6941 6941
Branches 1172 1172
=======================================
Hits 5716 5716
Misses 1120 1120
Partials 105 105
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
aws-cdk-automation
added
the
pr/needs-maintainer-review
| update_added_on: | ||
| if: github.repository == 'aws/aws-cdk' | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
|
|
||
| - name: Update AddedOn field | ||
| uses: actions/github-script@v7 | ||
| with: | ||
| github-token: ${{ secrets.PROJEN_GITHUB_TOKEN }} | ||
| script: | | ||
| const script = require('./scripts/prioritization/update-added-on.js') | ||
| await script({github}) |
There was a problem hiding this comment.
Just a design question: why do we decide to have separate workflow files? i.e. If there's 5 more columns we want to add in the future then there'll be 5 separate workflows for it right?
There was a problem hiding this comment.
Valid concern. we decided to have separate workflow based on the trigger type for specific automation. For this case, this workflow will have a cron schedule to check every 6 hours. We will be using the same workflow or any other existing workflow in future for other columns as a additional job step if it is also needed similar schedule.
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
This pull request has been removed from the queue for the following reason: The pull request can't be updated You should update or rebase your pull request manually. If you want to requeue this pull request, you can post a |
aws-cdk-automation
removed
the
pr/needs-maintainer-review
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Comments on closed issues and PRs are hard for our team to see. |
Issue # (if applicable)
NA
Reason for this change
Currently in the Prioritization dasboard, we don't have a way to filter the PRs and Issues by date when it is added.
Description of changes
This PR enables automation for adding current date to the
AddedOncolumn field in the Github Prioritization dasboard whenever new PR/Issues are being added to the dashboard.Describe any new or updated permissions being added
NA
Description of how you validated changes
Tested in test dashboard.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license