👩💻GitHub
Two-way sync for your developers to be connected with your team and community
Last updated
Two-way sync for your developers to be connected with your team and community
Last updated
Creating issues in GitHub will automatically create tasks in Dework and tasks can be linked to pull requests to automatically update their status.
This is an overview of this integration's basics. For a more practical guide, see 🖥 Bountied Issues with Github + Dework
You will be able to configure the GitHub integration by going to a project’s Settings, under the Integrations tab.
One project can be connected to many repositories at the same time.
It’s a two-way sync: you can both create Tasks from your GitHub Issues and create Issues from your Dework Tasks.
If selected when connecting the repo, it will import all existing issues from that repo to Dework. New Dework tasks will be created and things like issue Name, Description and Labels will carry over.
This is enabled by default. New issues created in your GitHub repository will automatically create tasks in the To Do column of your Dework project. Some metadata like issue Name, Description and Labels will carry over.
You can decide to enable it right after selecting a repository to connect in your project Settings. When creating a task in your project on Dework, it will automatically create an issue in your GitHub repository.
For bigger GitHub repos, you might not always want to sync all issues to Dework. When adding a repo, you can select which labels should be synced
Note: If your repos are already connected, you will need to disconnect & reconnect to enable this
After connecting a repository to a project, we will automatically generate branch names for your tasks that you can then use to link a specific task to a new branch.
Ex: git checkout -b jala/dw-2208/show-onboarding-flow-for
This branch name can be found when clicking the Link GitHub Branch button on your tasks.
Automation: After linking a task to a branch, if a Pull Request is opened, the task’s status will automatically change to In Review. Then, if the PR is merged, the task will move to Done.
