chore: use different approach to authenticate user in request-cli-integ-test

.github/workflows/README.md

@@ -5,62 +5,82 @@ These workflows and actions are configured in the AWS CDK GitHub repository.
 ## Pull Request Triggered
 
 ### Auto Approve
+
 [auto-approve.yml](auto-approve.yml): Approves merging PRs with the
 `auto-approve` label.
 Owner: Core CDK team
 
 ### PR Linter
+
 [pr-linter.yml](pr-linter.yml): Runs `tools/@aws-cdk-prlint` on each PR to
 check for correctness.
 Owner: Core CDK team
 
 ### v2-main PR automation
+
 [v2-pull-request.yml](v2-pull-request.yml): Runs `pkglint` on merge forward PRs
 and commits the results.
 Owner: Core CDK team
 
 ### Label Assigner
+
 [issue-label-assign.yml](issue-label-assign.yml): Github action for automatically adding labels and/or setting assignees when an Issue or PR is opened or edited based on user-defined Area
 Owner: CDK support team
 
 ### PR Labeler
-[pr-labeler.yml](pr-labeler.yml): GitHub action for automatically porting triage labels from issues 
+
+[pr-labeler.yml](pr-labeler.yml): GitHub action for automatically porting triage labels from issues
 linked in the PR description to the PR.
 Owner: Core CDK team
 
 ### GitHub Merit Badger
+
 [github-merit-badger.yml](github-merit-badger.yml): GitHub action that adds 'merit badges' to pull
 requests based on the users prior contributions to the CDK.
 Owner: Core CDK team
 
+### Request CLI Integ Test
+
+[request-cli-integ-test.yml](request-cli-integ-test.yml):
+Checks for relevant changes to the CLI code and requests a deployment to the `test-pipeline` environment.
+When approved this pushes the PR to the testing pipeline,
+thus starting the cli integ test build.
+Owner: Core CDK team
+
 ## Issue Triggered
 
 ### Closed Issue Message
+
 [closed-issue-message.yml](closed-issue-message.yml): Adds a reminder message
 to issues that are closed.
 Owner: CDK support team
 
 ### Label Assigner
+
 [issue-label-assign.yml](issue-label-assign.yml): Github action for automatically adding labels and/or setting assignees when an Issue or PR is opened or edited based on user-defined Area
 Owner: CDK support team
 
 ## Scheduled Actions
 
 ### Issue Lifecycle Handling
+
 [close-stale-issues.yml](close-stale-issues.yml): Handles labeling issues and
 PRs with `closing-soon`, `response-requested`, etc.
 Owner: CDK support team
 
 ### Yarn Upgrader
+
 [yarn-upgrade.yml](yarn-upgrade.yml): Upgrades yarn dependencies and creates a
 patch file for downloading.
 Owner: Core CDK team
 
 ### Issue Reprioritizer
+
 [issue-reprioritization.yml](issue-reprioritization.yml): GitHub action that labels `p2`
 issues as `p1` if a certain level of community engagement is met.
 Owner: Core CDK team
 
 ### Issue Metrics
-[issue-metrics.yml](issue-metrics.yml): GitHub action that runs monthly to report on metrics for issues created last month.
-Owner: Core CDK team
+
+[repo-metrics.yml](repo-metrics.yml): GitHub action that runs monthly to report on metrics for issues and PRs created last month.
+Owner: Core CDK team

.github/workflows/request-cli-integ-test.yml

@@ -35,14 +35,15 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v3
         with:
+          token: ${{ secrets.PROJEN_GITHUB_TOKEN }}
           ref: ${{ github.event.pull_request.head.ref }}
           repository: ${{ github.event.pull_request.head.repo.full_name }}
       - name: Submit to test-pipeline
         # Needs to run with PROJEN_GITHUB_TOKEN because we need permissions to force push the branch
         run: |
           git config --global user.name 'aws-cdk-automation'
           git config --global user.email 'aws-cdk-automation@users.noreply.github.com'
-          git push --force --atomic https://oauth2:${{ secrets.PROJEN_GITHUB_TOKEN }}@github.com/${{ github.repository }}.git FETCH_HEAD:test-main-pipeline
+          git push --force --atomic ${{ github.repositoryUrl }} FETCH_HEAD:test-main-pipeline
       - name: Explain next steps
         uses: thollander/actions-comment-pull-request@v2
         with: