Hashi is a bridge to sync issues & tasks between Github and Asana.
I like Asana a lot, it has definitely revolutionized the way I manage my time and work flow. I also really like Github, but really hated having to keep track of my assigned issues on Github and in Asana. So, I made Hashi to help do that for me.
There are other services that allow you to do this, but their free tiers had limits that were annoying.
I've only tested this running on Ubuntu, so ymmv on other platforms. If you are
using something with apt-get, install is as easy as running the install.sh
script included. Once you have run this script successfully, you can go ahead
and skip the rest of this section.
Note: If you already have MongoDB installed, you need to enable text search, see below for more information.
If you are not, then you need to get the following dependencies installed:
Note: You need to enable text search capabilities on MongoDB. To do this, add the following line to your mongodb.conf
setParameter=textSearchEnabled=true
You will also need to run npm install to get the node module dependencies for
this project.
You define a "binding" between a Github repository and an Asana project. Hashi will then sync all Github issues for the repository that are assigned to the specified user to Asana. This includes sync'ing completion status in real time.
However, this sync only goes one way. If you complete a task in Asana, the Github issue will not be closed. This support can be added, but for my work flow, it really only made sense to close issues on Github. If this is a feature you'd like to see, let me know.
See config.js for
information on how to configure Hashi. I believe the comments make it fairly
clear what to do, but let me know if you find anything confusing in the Github
Issues.
Note: Make sure to open the appropriate port in your firewall, and see Webhook Security below for information on how to keep this secure.
You can run Hashi any number of ways, but the way that I've tested that seems to work the best is using a node module called forever.
If you decide to use forever, I've included a start.sh script to help get you up and running quickly. If you don't want to have to keep specifying your credentials at each startup, you need to set 3 environment variables.
githubUsername- This is the Github username which will be used to authenticate all Github API requests.githubPassword- This is the password associated with the Github account.asanaKey- This is the Asana API key that will be used to authenticate all Asana requests.
Information about how to find your Asana API key can be found here
Hashi creates a webhook on your Github repository that will be used to notify Hashi anytime an issue is open/closed/changed. The "easiest" way to get Hashi up and running would be to give the whole world access to the port; however, this is not advised, please, do not do this. Now, the better way to do this is only allow Github'd IPs to ping the port. You can find these IPs by going to the repository's administration page. Then navigate to the "Service Hooks" section and click on "WebHook URLs". Here, it should list the public IP address that the hooks will originate from.
Quickest way to get a bug fixed or see a new feature added is to submit a pull request :) If that isn't your style though, head to the issues sections.
If you are reporting a bug, please include code/data/something to reproduce the issue.