ci(catalog): default commit_sha to latest foundry-samples@main#423
Merged
Yimin-Jin merged 1 commit intoJun 2, 2026
Merged
Conversation
Make the workflow_dispatch `commit_sha` input optional. When the user leaves it blank, a new `Resolve commit SHA` step queries the GitHub API for the current tip of `microsoft-foundry/foundry-samples@main` and pins the catalog generation to that SHA. - `commit_sha`: required=false, default empty. - New step uses `gh api` (default GITHUB_TOKEN, contents:read is enough for a public repo) and validates the result looks like a SHA before using it. - The pinned SHA + its source (user input vs. resolved-from-main) is echoed to the step summary so reviewers can see what the run targeted. - `Generate sample catalog` now reads from `steps.resolve-sha.outputs.sha` instead of `inputs.commit_sha` directly.
huimiu
approved these changes
Jun 2, 2026
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
2 participants
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.
Why
Cherry-pick of #418 to
template/pre-releaseso the optionalcommit_shabehaviour is available on every dispatchable branch(
template/devvia #418,template/stablevia #422,template/pre-releasevia this PR).Today the
Sync Sample Catalogworkflow requires the dispatcher to pastea specific
foundry-samplesSHA. In practice we almost always want thetip of
main, so the lookup step is friction without value.What
commit_shainput becomes optional (default empty).Resolve commit SHAstep:gh api repos/microsoft-foundry/foundry-samples/commits/mainand pin to that SHA;Generate sample catalogreads fromsteps.resolve-sha.outputs.sha.to `` so reviewers can see what the run targeted.
Verbatim cherry-pick of #418 - no script changes.
Smoke test
YAML lints clean. Functional verification will happen on the next
workflow_dispatchfromtemplate/pre-releaseonce this merges.