Keep your Context7 documentation in sync by triggering a refresh whenever you push to your main branch.Documentation Index
Fetch the complete documentation index at: https://context7.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Setup
Get your API key
Go to your Context7 dashboard and copy your API key.
Add the API key as a repository secret
In your GitHub repository, go to Settings → Secrets and variables → Actions and add a new secret:
| Name | Value |
|---|---|
CONTEXT7_API_KEY | Your API key from the Context7 dashboard |
Create the workflow file
Add the following file to your repository at This uses
.github/workflows/context7-refresh.yml:${{ github.repository }} to automatically resolve to your repository’s owner/repo (e.g., vercel/next.js). If your library identifier on Context7 differs from your GitHub repository name, replace it with the correct value (e.g., /your-org/your-repo).Refreshing a Specific Branch
To refresh a non-default branch, add thebranch field to the request body. The branch value must match a branch name that already exists on your library in Context7.
If the branch has not been added to your library on Context7, the refresh will fail with a
branch_not_found error.Private Repositories
For private repositories, include agitToken so Context7 can access your code:
Private sources require a Pro or Enterprise plan. See the Private Sources guide for more details.