GitHub Action¶
The official GitHub Action can be used to configure Uplift within your workflow. As Uplift is designed to push changes back to your repository, you will need to provide it with an access token1. This is by design.
- Setting a
fetch-depth
of 0 will ensure all tags are retrieved, which is required by Uplift to determine the next semantic version - When you use the repository's
GITHUB_TOKEN
to perform tasks, events triggered by theGITHUB_TOKEN
will not create a new workflow run.
Triggering another Workflow¶
To ensure Uplift triggers another workflow run when tagging the repository, a personal access token should be created and stored as a secret. This will then replace the default GITHUB_TOKEN
as follows:
-
It is best security practice to create an access token with the shortest possible expiration date. ↩