feat: add git-sha parameter to support deploying from specific commits#228
Merged
feat: add git-sha parameter to support deploying from specific commits#228
Conversation
c1b3b05 to
2d75dc9
Compare
Add optional git-sha input parameter to deploy workflows to enable building and deploying from specific commit SHAs. This enables PR comment-based deployments where a specific commit needs to be built. Changes: - Add git-sha input to component-build.yml - Pass SHA through setup job outputs for consistency - Update all checkouts and image tags to use the provided SHA - Add git-sha input to deploy-generic.yml, deploy-generic-v2.yml, deploy-kotlin.yml, deploy-python.yml - Defaults to github.sha when not provided (backwards compatible)
2d75dc9 to
db9bbbb
Compare
There was a problem hiding this comment.
Pull request overview
This PR adds support for building and deploying from specific commit SHAs by introducing an optional git-sha parameter to the build and deployment workflows. This enables PR comment-based deployments and other scenarios where a specific commit needs to be built instead of the default triggering commit.
Changes:
- Added optional
git-shainput parameter to all deployment workflows (deploy-generic, deploy-generic-v2, deploy-kotlin, deploy-python) - Updated component-build.yml to accept and use git-sha for checkouts, image tagging, and outputs
- Changed Docker metadata action from automatic SHA detection to explicit raw value to ensure consistency
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/component-build.yml | Added git-sha input parameter; updated all checkouts, image tags, and outputs to use the provided SHA or default to github.sha |
| .github/workflows/deploy-generic.yml | Added git-sha input parameter and passed it through to component-build workflow |
| .github/workflows/deploy-generic-v2.yml | Added git-sha input parameter and passed it through to component-build workflow |
| .github/workflows/deploy-kotlin.yml | Added git-sha input parameter and passed it through to component-build workflow |
| .github/workflows/deploy-python.yml | Added git-sha input parameter and passed it through to component-build workflow |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
prasad-manu
approved these changes
Feb 6, 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
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.
Add optional git-sha input parameter to deploy workflows to enable building and deploying from specific commit SHAs. This enables PR comment-based deployments where a specific commit needs to be built.
Changes
git-shainput tocomponent-build.ymlgit-shainput todeploy-generic.yml,deploy-generic-v2.yml,deploy-kotlin.yml,deploy-python.ymlUsage
Calling workflows can now pass a specific SHA to build:
Backwards compatible
The
git-shaparameter is optional and defaults togithub.sha, so existing workflows continue to work without changes.