GitHub and GitHub Enterprise

GitHub is a popular web-site for hosting Git repositories. It also offers Issues management, similar to bug trackers like MantisBT and JIRA. Although GitHub’s issues management is quite simple (it lacks time estimates and many other features), it is actually very convenient, fast and user friendly.

Sometimes you need to export your tasks from Microsoft Project, Atlassian JIRA or other systems to GitHub. This is when Task Adapter comes in handy. It helps you to keep your GitHub or GitHub Enterprise issues in sync with whatever other system you have, or lets you export tasks to Microsoft Project.

Configure GitHub connection

The first time you are configuring an integration for GitHub or GitHub Enterprise in TaskAdapter, you need to set up your GitHub connection - URL and credentials.

  • Server URL GitHub or GitHub Enterprise URL. While many open-source developers and small companies typically only use https://github.com, there is also a downloadable version of the same service called GitHub Enterprise. This is a version of GitHub that is installed locally inside your company network and lets you stay in control over your data, which is a must-have for the majority of mid-size and large-size companies. If you use GitHub Enterprise, you can change the default URL from https://github.com to whatever your URL is (say, https://ghe.mycompany.com)
  • Login Your GitHub login
  • Password Your GitHub password

Remember that, unlike in a cloud-based integration solution, your GitHub credentials stay with you and are never transmitted outside of your company (well, except when authenticating against github.com, of course).

Configure GitHub endpoint

Once you configured a GitHub or GitHub Enterprise connection in the previous step, now you can set up details for the current integration config in TaskAdapter.

GitHub configuration dialog supports the following options:

GitHub configuration dialog

  • Repository ID Your GitHub repository ID
  • Query Any text query allowed by GitHub. Task Adapter does not interpret this query. It just just sends it as-is to the configured GitHub connection to load data. Sample value: milestone=7&state=closed