Add daily workflow to sync Review Date from issue descriptions and comments to GitHub Projects V2 with PR linking

[Copilot]

Review Date Sync GitHub Action - Spell Check Fix ✅

Summary

Fixed cspell configuration to allow the "ampm" variable name used in the sync-review-date.js file.

Changes Made

• Added override section in .github/cspell.yaml for sync-review-date.js
• Added "ampm" to the allowed words list for this specific file

Verification

• ✅ CSpell check passes: 0 issues found in sync-review-date.js
• ✅ Follows the pattern used by other files in the cspell.yaml configuration

File Modified: .github/cspell.yaml

This resolves the PR check complaint about the "ampm" variable name.

Original prompt

Create a GitHub Action that runs once a day and checks all open issues in the repository. For each issue, if the issue description contains a date in the format 'Review Date: YYYY-MM-DD', update the 'Review Date' custom field for the corresponding item in Azure org's project 196 to that date. The action should:

• Use the GitHub API to list all open issues.
• Parse each issue description for a line like 'Review Date: YYYY-MM-DD'.
• Use the GitHub Projects GraphQL API to locate the corresponding project item for the issue in project 196 in the Azure organization.
• Set the 'Review Date' custom field for the item in Project 196 to the date found in the issue description, if it is present.
• Skip issues where no date is found in the required format.
• Use a secure approach for authentication (e.g., GitHub token via secrets). Provide clear code comments and minimal documentation in the repo.

This pull request was created as a result of the following prompt from Copilot chat.

Create a GitHub Action that runs once a day and checks all open issues in the repository. For each issue, if the issue description contains a date in the format 'Review Date: YYYY-MM-DD', update the 'Review Date' custom field for the corresponding item in Azure org's project 196 to that date. The action should:

• Use the GitHub API to list all open issues.
• Parse each issue description for a line like 'Review Date: YYYY-MM-DD'.
• Use the GitHub Projects GraphQL API to locate the corresponding project item for the issue in project 196 in the Azure organization.
• Set the 'Review Date' custom field for the item in Project 196 to the date found in the issue description, if it is present.
• Skip issues where no date is found in the required format.
• Use a secure approach for authentication (e.g., GitHub token via secrets). Provide clear code comments and minimal documentation in the repo.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[github-actions[bot]]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ The required check named Protected Files has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

Comment generated by summarize-checks workflow run.

[Copilot]

@copilot please make these changes.

Changes completed in commit ba59ecf:

• Updated date format to MM/DD/YYYY HH:MM AM/PM PT
• Added filtering for "api-review-scoping" label
• Updated documentation and tests
• All 13 tests passing

[Copilot]

A few more refinements.

All refinements completed in commit f9aa4b3:

• Label updated to "API Review Scoping"
• Comment scanning with last-date logic
• PR linking functionality
• All tests passing (13/13)