alvelive/Update Action File
Simple GitHub action for updating a template file
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit May 24, 2024
- License
- None
Pinned Snippet
uses: alvelive/update-action@d515e0e053a459a765b0a92155c70f58dda1e347 # no releases — HEAD as of 2026-07-10tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | GitHub actions token to commit to repository. Can be obtained from `secrets.GITHUB_TOKEN` context. | yes | — |
| github-username | Username to be used in commit | yes | GitHub Actions |
| github-email | Email to be used in commit | yes | actions@github.com |
| repository | The repository to push the changes to. Can be obtained from the `github.repository` context. Example value is 'alvelive/update-action' | yes | — |
| branch | The branch to push the changes to. Can be obtained from the `github.head_ref` context for pull_request or `github.ref_name` for push. Example value is 'main', 'user/feture-branch' etc. | yes | — |
| sha | The commit SHA to be used to construct base_url. Can be obtained from the `github.sha` context. | yes | — |
| template | The file to read the input from | yes | action-template.yml |
| output | The file to write the output to | yes | action.yml |
| match | The string to replace | yes | {{base_url}} |
| replace | The string to replace with | no | — |
Outputs
no outputs