-
Notifications
You must be signed in to change notification settings - Fork 4
AAE-38169 Allow controlling the git SHA when creating a gh deployment status #1165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
atchertchian
merged 4 commits into
master
from
improvement/AAE-38169-allow-sha-deployment-status
Oct 2, 2025
Merged
AAE-38169 Allow controlling the git SHA when creating a gh deployment status #1165
atchertchian
merged 4 commits into
master
from
improvement/AAE-38169-allow-sha-deployment-status
Oct 2, 2025
Conversation
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Adds ability to specify a custom git SHA when creating a GitHub deployment so that deployments can reference commits other than the workflow trigger commit.
- Introduces new input git-sha to github-deployment-create action and wires it into deployment creation.
- Updates README with a brief note about optional SHA.
- Bumps version to v9.2.0 (minor feature addition).
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
File | Description |
---|---|
version.txt | Minor version bump to reflect new optional input feature. |
docs/README.md | Adds a sentence noting an optional git SHA can be provided (may need fuller parameter documentation). |
.github/actions/github-deployment-create/action.yml | Adds git-sha input and uses it (with fallback) when creating the deployment. |
gionn
reviewed
Oct 2, 2025
Co-authored-by: Giovanni Toraldo <[email protected]>
atchertchian
commented
Oct 2, 2025
Co-authored-by: Copilot <[email protected]>
gionn
approved these changes
Oct 2, 2025
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.
Checklist
Description