Seamlessly connect your GitHub repositories to t0ggles and sync issues, pull requests, and task statuses across both platforms.
Before using any GitHub-related features, you need to connect your repositories:
Once connected, you'll be able to link issues, pull requests, and automate task creation.
When a task is linked to a GitHub issue or pull request:
A GitHub tag appears on the task card, showing the issue/PR number and its status (open or closed)
Clicking the tag opens a context menu with options to:
You can automatically create and link a task from a GitHub issue or pull request by using a special comment:
t0ggles-create {Project Key}
Example:
To create a task in a project with the key CLIENTS
, add this to the issue or PR:
t0ggles-create CLIENTS
The task will be created and immediately linked to the GitHub item.
You have two options to link an existing t0ggles task:
Include the task key (e.g., CLIENTS-131
) in the title of the issue or pull request.
Add this command in the description or as a comment:
t0ggles-link {Task Key}
Example:
t0ggles-link CLIENTS-131
When creating a task in t0ggles, you can simply paste the URL of a GitHub issue or pull request into the task title.
t0ggles will:
Tasks can be automatically marked as Done when related GitHub branches or commits are merged:
Create a branch with the task key (e.g., CLIENTS-131
).
Upon merging into the main (or master) branch, the task is moved to Done.
Include the following command in a commit message:
t0ggles-fixes {Task Key}
Example:
t0ggles-fixes CLIENTS-131
Upon merge, the task will be moved to Done.
When a GitHub issue or pull request is closed, the task is moved to Done.
To remove the GitHub link from a task:
t0ggles-unlink
Or