Skip to content

Commit 5a3b4a4

Browse files
authored
Update github-actions.mdx (#1222)
1 parent f91a118 commit 5a3b4a4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/v3/github-actions.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "GitHub Actions"
33
description: "You can easily deploy your tasks with GitHub actions."
44
---
55

6-
This simple GitHub action file will deploy you Trigger.dev tasks when new code is pushed to the `main` branch and the `trigger` directory has changes in it.
6+
This simple GitHub action file will deploy your Trigger.dev tasks when new code is pushed to the `main` branch and the `trigger` directory has changes in it.
77

88
<Warning>
99
The deploy step will fail if any version mismatches are detected. Please see the [version
@@ -77,7 +77,7 @@ jobs:
7777
7878
If you already have a GitHub action file, you can just add the final step "🚀 Deploy Trigger.dev" to your existing file.
7979
80-
You need to add the `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.
80+
You need to add the `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"](https://cloud.trigger.dev/account/tokens) tab.
8181

8282
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.
8383

0 commit comments

Comments
 (0)