fix: Pin GitHub Actions to commit SHAs - #178
Open
PrekshithD-Microsoft wants to merge 1 commit into
Open
Conversation
PrekshithD-Microsoft
requested review from
Avijit-Microsoft,
Roopan-Microsoft,
Anish Arora (aniaroramsft),
dgp10801 and
Todd Herman (toherman-msft)
as code owners
August 17, 2026 11:38
Contributor
There was a problem hiding this comment.
Pull request overview
This PR aims to harden and stabilize CI/CD by pinning GitHub Actions to immutable commit SHAs (instead of floating tags), improving supply-chain security and workflow reproducibility.
Changes:
- Pinned multiple GitHub Actions
uses:references (e.g.,actions/checkout,azure/login,actions/stale,lychee-action, semantic PR title checker) to specific commit SHAs. - Updated the azd template validation workflow to use a pinned SHA for
microsoft/template-validation-action.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/stale-bot.yml | Pins actions/stale to a commit SHA. |
| .github/workflows/pr-title-checker.yml | Pins the semantic PR title checker action to a commit SHA. |
| .github/workflows/broken-links-checker.yml | Pins actions/checkout and lycheeverse/lychee-action to commit SHAs. |
| .github/workflows/azure-dev.yml | Pins actions/checkout, Azure/setup-azd, and azure/login to commit SHAs. |
| .github/workflows/azd-template-validation.yml | Pins actions/checkout and microsoft/template-validation-action to commit SHAs. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| steps: | ||
| - name: Checkout Repo | ||
| uses: actions/checkout@v4 | ||
| uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates workflow files to improve security and maintainability by pinning GitHub Actions to specific commit SHAs instead of floating tags. Additionally, it enhances the deployment process by adding a user notice before provisioning. Below are the most important changes grouped by theme:
Security and Maintenance: Pinning GitHub Actions to SHAs
actions/checkoutusages in workflow files (such as.github/workflows/azd-template-validation.yml,azure-dev.yml,broken-links-checker.yml) to reference a specific commit SHA instead of a version tag, ensuring builds use a known, immutable version. [1] [2] [3]microsoft/template-validation-action,Azure/setup-azd,azure/login,lycheeverse/lychee-action,amannn/action-semantic-pull-request,actions/stale) to specific SHAs in their respective workflow files for improved security and reproducibility. [1] [2] [3] [4] [5] [6] [7]Deployment Experience Improvement
azure.yamlto display a deployment notice to users, encouraging them to open an issue with logs if deployment fails, improving user guidance and support.## PurposeDoes this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information