Skip to content

Commit 2473153

Browse files
committed
coderabbit changes
1 parent b9efde3 commit 2473153

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

docs/guides/examples/vercel-sync-env-vars.mdx

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,14 +7,17 @@ description: "This example demonstrates how to sync environment variables from y
77
import VercelDocsCards from "/snippets/vercel-docs-cards.mdx";
88

99
<Warning>
10-
**`syncVercelEnvVars` is deprecated.** If you are using the [Vercel
11-
integration](/vercel-integration), do not use this extension — the integration handles environment
12-
variable syncing natively. Using both together can cause env vars to be incorrectly populated.
10+
**Deprecated when using the Vercel integration.** If you are using the [Vercel
11+
integration](/vercel-integration), do not use `syncVercelEnvVars` — the integration handles env
12+
var syncing natively and using both together can cause env vars to be incorrectly populated.
13+
14+
If you are **not** using the Vercel integration, `syncVercelEnvVars` is still supported. Continue
15+
with the configuration below.
1316
</Warning>
1417

1518
## Build configuration
1619

17-
To sync environment variables, you just need to add our build extension to your `trigger.config.ts` file. This extension will then automatically run every time you deploy your Trigger.dev project.
20+
If you are not using the [Vercel integration](/vercel-integration), you can sync environment variables manually by adding the `syncVercelEnvVars` build extension to your `trigger.config.ts` file. This extension will run automatically every time you deploy your Trigger.dev project.
1821

1922
<Note>
2023
You need to set the `VERCEL_ACCESS_TOKEN` and `VERCEL_PROJECT_ID` environment variables, or pass

0 commit comments

Comments
 (0)