Rollout to your repositories
Connect Tessl to your codebase to automatically generate, evaluate, and optimize context!
Last updated
Connect Tessl to your codebase to automatically generate, evaluate, and optimize context!
Configure and update multiple codebases automatically with pull requests
Tessl connects directly to GitHub and GitLab so you can initialize repositories and rollout shared guidance (coding standards, conventions, and agent instructions) across your codebase, automatically through pull requests (PRs).
Without this integration, teams rely on manual edits, onboarding docs, or one-off repo configuration. With the Tessl integrated, Tessl can use branches and PRs to:
add the configuration files needed to use Tessl (tessl.json, .mcp.json)
update those files as your guidance evolves
apply the same guidance to multiple repositories in a single action
keep every change visible, reviewable, and merge-controlled
Nothing is applied directly to your codebases, every update ships as a PR you review and merge like any other change.
Once GitHub or GitLab access is enabled, you can perform three core actions:
Tessl generates a PR that may include:
a new or updated tessl.json
a .mcp.json file enabling Tessl as an MCP server
You merge whenever you're ready.
From the Tessl interface, you can select a guidance resource and generate pull requests across multiple repositories at once. This capability is helpful for rolling out:
coding conventions
architectural patterns
internal standards
agent instructions
Uninstall the integration and remove the connection from Tessl.
This documentation walks through five workflows:
Permissions Required permissions in Tessl and integration
Enable the GitHub App so Tessl can create pull requests.
Connect Tessl to GitLab Configure GitLab so Tessl can create pull requests.
Use the Setup action to generate configuration inside a repository.
Select a resource and generate PRs across the repositories you choose.
Uninstall the integration and remove the connection from Tessl.
*Each workflow ends with a pull request, reviewed and merged through your normal development process.
Last updated

