|`APP_NAMESPACE`| The namespace where the application is deployed to. For example,`gitops`.| ✅| ✅|

|`APP_NAME`| The name of the specific application the Promotion Workflows and the Promotion Action pertain to. For example,`trioapp-staging`.| ✅| ✅|

|`REPO_URL`| The Git repository with the application settings, as defined in the application's configuration. See[Source settings for applications]({{site.baseurl}}/docs/deployments/gitops/create-application/#sources).| ✅| ✅|

|`BRANCH`| The specific Git branch to which to promote changes. For example,`main`.|✅| ✅|

|`BRANCH`| The specific Git branch to which to promote changes, retrieved from`spec.source.targetRevision` defined in the application's configuration settings. <br>If`spec.source.targetRevision` is set to`HEAD`, this is the value used for`BRANCH` in both the Pre- and Post-Action Workflows, even if the resolved branch name is`main`,`master`, or any custom name.|✅| ✅|

|`PATH`| The relative path within the repository defined by`REPO_URL` to the directory or file containing the application's configuration. See[Source settings for applications]({{site.baseurl}}/docs/deployments/gitops/create-application/#sources).| ✅| ✅|

|`RUNTIME`|The name of the GitOps Runtime the application being promoted is associated with.|✅| ✅|

|`COMMIT_SHA`| The unique identifier (SHA) of the commit, generated by Git, including the precise set of changes addressed by the commit. Can be used as a trigger condition in Promotion Flows configured for a product.||✅|

|`COMMIT_AUTHOR`| The name of the user who made the commit. Useful for tracking changes and for notifications.|| ✅|

|`COMMIT-MESSAGE`| The text in the commit message associated with the code change that triggered the promotion, providing context for the changes introduced by the commit.||✅|

|`COMMIT-DATE`| The date and time when the commit was made. Useful to correlate the commit with other events and understand the timeline of changes.|| ✅|

|`COMMIT_SHA`| The unique identifier (SHA) of the commit, generated by Git, including the precise set of changes addressed by the commit. Can be used as a trigger condition in Promotion Flows configured for a product.<br>Available in Post-Action Workflows only for commit-based Promotion Actions. Not available for PR-based Promotion Actions.||✅|

|`COMMIT_AUTHOR`| The name of the user who made the commit. Useful for tracking changes and for notifications.<br>Available in Post-Action Workflows only for commit-based Promotion Actions. Not available for PR-based Promotion Actions.|| ✅|

|`COMMIT-MESSAGE`| The text in the commit message associated with the code change that triggered the promotion, providing context for the changes introduced by the commit.<br>Available in Post-Action Workflows only for commit-based Promotion Actions. Not available for PR-based Promotion Actions.||✅|

|`COMMIT-DATE`| The date and time when the commit was made. Useful to correlate the commit with other events and understand the timeline of changes.<br>Available in Post-Action Workflows only for commit-based Promotion Actions. Not available for PR-based Promotion Actions.|| ✅|