Written by Chessboard · Updated 2026-10-12
Connect the workspace
Open the workspace's Connections area and connect the Chessboard GitHub App. When installing, use Only select repositories and choose the repositories you want to make available.
A GitHub installation and a Chessboard workspace connection are separate steps. An installed app can have repository access even before Chessboard has finished linking that installation to your workspace.
Choose repositories for the team
After the connection loads, enable the relevant repository for the team that owns the work. This controls which linked repository observations can be visible to people who can view that team.
Review the team's visibility before connecting private repository work. Issue and pull-request descriptions may themselves contain sensitive information.
Link existing work
Open a task and use its relationships and evidence area to link an existing issue or pull request. Repository state, reviews and available checks can then provide context alongside the task.
A passing check is one piece of evidence. It does not independently prove that every acceptance condition has been met. A merged pull request does not silently mark a Chessboard task Done.
Use a deliberately bounded integration
Chessboard's supported integration requests read access to repository metadata, issues, pull requests, checks and commit statuses. It does not request repository Contents or write permissions.
The application restricts which GitHub endpoints it uses. This is not a promise that repository-related text can never contain source snippets; people can paste those into issue descriptions, pull requests or check payloads.
Know what the connection does today
Chessboard currently does not offer bidirectional GitHub issue synchronization, source-code editing or automatic task completion. Keep the repository as the place for repository work and Chessboard as the place for the team's planning decisions.
If an observation is missing, check the workspace connection, selected repository and team enablement before changing permissions.