GitHub
Mention GitHub issues in Cycle docs, create issues in bulk and update their status without switching tools.
Last updated
Mention GitHub issues in Cycle docs, create issues in bulk and update their status without switching tools.
Last updated
Looking to connect product delivery and discovery? You're in the right place. Here's everything you need to know about integrating GitHub issues with Cycle.
Follow these steps or click the interactive step-by-step tutorial below 👇
Open your Cycle workspace settings and scroll down to "Integrations"
On the right, next to "Collaboration," click on "Add new" and select "GitHub issues"
Log in to your GitHub account and select your repository
Copy the URL of the GitHub project you want to sync with Cycle and paste it under the GitHub issues integration card
The GitHub repository must belong to a GitHub organization. Only organization owners can set up this integration. You can have multiple Github projects linked.
Since you added the GitHub integration, you probably have existing issues over there that aren't tied to a product requirement document (PRD).
No worries, you can easily mention existing GitHub issues in Cycle using the "/GitHub issue" command.
This will also add a comment in GitHub with a link to the corresponding Cycle doc so you can easily have everyone on the same page.
To edit a mentioned issue, click the down-facing arrow to the left of the GitHub issue to expand it. From here, you can edit its status. Every edit, no matter which tool it was made from, is safely synced in GitHub and Cycle at all times.
To create a single GitHub issue, highlight any text in a Cycle doc and click on the GitHub icon in the toolbar. You can also use the keyboard shortcut "⌘+2".
To create multiple issues at once, highlight a bullet list of issues to create, and use the GitHub icon in the toolbar or the keyboard shortcut, ⌘+3.
Note: Creating GitHub issues in bulk will only work on bullet lists.
Once all GitHub issues in a Cycle doc have been set as "Done", Cycle will automatically update the doc's status so that customer-facing teams know they can close the feedback loop.
