Skip to content

docs: add branchName and repoName as general template variables #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vigneshrajsb merged 1 commit into from
Mar 12, 2026
Merged

docs: add branchName and repoName as general template variables #24

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/pages/docs/features/_meta.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,5 +47,5 @@ export default {
},
"mcp-integration": {
"title": "MCP Integration"
},
}
};
3 changes: 3 additions & 0 deletions src/pages/docs/features/template-variables.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ tags:
- publicUrl
- sha
- branchName
- repoName
- UUID
- internalHostname
- review
Expand All @@ -27,6 +28,8 @@ The following template variables are available for use within your configuration
- **`{{{buildUUID}}}`** - The unique identifier for the Lifecycle environment, e.g., `lively-down-881123`.
- **`{{{namespace}}}`** - Namespace for the deployments, e.g., `env-lively-down-881123`.
- **`{{{pullRequestNumber}}}`** - The GitHub pull request number associated with the environment.
- **`{{{branchName}}}`** - The branch name of the pull request that triggered the environment.
- **`{{{repoName}}}`** - The full repository name (e.g., `org/repo`) associated with the environment.

### Service-Specific Variables

Expand Down
Loading