You can easily deploy your tasks with GitHub actions.
main
branch and the trigger
directory has changes in it.
TRIGGER_ACCESS_TOKEN
secret to your repository. You can create a new access token by going to your profile page and then clicking on the “Personal Access Tokens” tab.
To set it in GitHub go to your repository, click on “Settings”, “Secrets and variables” and then “Actions”. Add a new secret with the name TRIGGER_ACCESS_TOKEN
and use the value of your access token.
@trigger.dev/*
package versions need to be in sync, otherwise there will be errors and unpredictable behavior. Hence, the deploy
command will automatically fail during CI on any version mismatches.
To ensure a smooth CI experience you can pin the CLI version in the deploy step, like so:
--version
to any command.