Skip to content
Azure DevOps logoGitHub logo

Connect Azure DevOps to GitHub

Move data between Azure DevOps and GitHub the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Azure DevOps triggers
2
Azure DevOps actions
6
GitHub triggers
14
GitHub actions
19

Automation ideas

What you can build with Azure DevOps and GitHub

A few flows teams run between Azure DevOps and GitHub. Use one as a starting point, or build your own from scratch.

  • New or Updated Work Item (Instant) in Azure DevOps creates Create Issue in GitHub

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New Pull Request in GitHub creates Create Work Item in Azure DevOps

    Triggers when there is activity on a pull request.

  • New or Updated Work Item (Instant) in Azure DevOps creates Get issue information in GitHub

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New Pull Request in GitHub creates Get Work Item in Azure DevOps

    Triggers when there is activity on a pull request.

  • New or Updated Work Item (Instant) in Azure DevOps creates Create comment on a issue in GitHub

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New Pull Request in GitHub creates Update Work Item in Azure DevOps

    Triggers when there is activity on a pull request.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Azure DevOps and acts in GitHub, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.