aaronsteers/Resolve CI Vars
Resolve variables using a combination of (1) pre-built resolutions, (2) static inputs, and (3) Jinja2 expressions.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Jan 1, 2026
- License
- MIT
Pinned Snippet
uses: aaronsteers/resolve-ci-vars-action@2e56afab0344bbe03c047dfa39bae559d0291472 # v0.1.6tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| static_inputs | Variable assignments in key=value format (multiline string). Each line should be in the format: variable_name=value | — | — |
| jinja_inputs | Jinja2 expression to evaluate (e.g. user or default_user) | no | — |
| repo | Optional. Target repository to resolve variables for (e.g. `myorg/my-repo``). If not provided, will use the current repository (github.repository) This is useful for resolving variables in a different repo than the one triggering the workflow. If it recommended to leave this omitted unless you are specifically doing cross-repo workflows. | no | "" |
| pr | Optional. PR number to resolve variables for (overrides auto-detection from workflow_dispatch inputs). | no | "" |
| comment_id | Optional. Comment ID to resolve variables for (overrides auto-detection from workflow_dispatch inputs). If not provided, can be automatically detected from a 'comment-id' workflow input, or the 'comment' github context. | no | "" |
| log_outputs | Whether to log the resolved value (default false). This can be enabled if inputs and outputs are non-sensitive. you can also use this for sensitive values IIF you are confident you have masked sensitive values using GitHub secret masking. | no | false |
| non_sensitive | Alias for log_outputs (true = show evaluated output) | no | false |
Outputs
| name | description |
|---|---|
| custom | JSON-encoded object with all resolved values |
| resolved-git-ref | Full Git ref (refs/heads/... or refs/tags/...) |
| resolved-git-branch | Short branch name (e.g. main, feature/foo) |
| resolved-git-sha | Commit SHA |
| resolved-git-tag | Tag name (if applicable) |
| resolved-repo-name | Repository name (e.g. my-repo) |
| resolved-repo-owner | Repository owner (user or org) |
| resolved-repo-name-full | Owner + name (e.g. myorg/my-repo) |
| pr-source-git-ref | Git ref of the source (PR head) |
| pr-source-git-branch | Branch name of the source |
| pr-source-git-sha | SHA of the source commit |
| pr-source-repo-name | Source repo name |
| pr-source-repo-owner | Source repo owner |
| pr-source-repo-name-full | Full source repo name (owner/name) |
| pr-source-repo-is-fork | Whether the source repo is a fork of the target repo |
| pr-target-git-ref | Git ref of the target (PR base) |
| pr-target-git-branch | Branch name of the target |
| pr-target-git-sha | SHA of the target commit |
| pr-target-git-tag | Tag name, if PR targets a tag |
| pr-target-repo-name | Target repo name |
| pr-target-repo-owner | Target repo owner |
| pr-target-repo-name-full | Full target repo name (owner/name) |
| pr-number | Pull request number (if applicable) |
| pr-url | URL to the pull request |
| pr-title | Title of the pull request |
| comment-id | ID of the triggering comment (if applicable) |
| comment-url | URL to the triggering comment (if applicable) |
| run-id | GitHub Actions run ID |
| run-url | URL to the GitHub Actions run |
| is-pr | Boolean: whether the current context is a PR |
| var1 | Custom user-defined output variable 1 |
| var2 | Custom user-defined output variable 2 |
| var3 | Custom user-defined output variable 3 |