The morning Fog of Howe Sound shrouds The Queen of Surrey as she pulls into Langdale Terminal
The view from The Lighthouse Pub
Laser Sailing: If your butt isn’t wet you’re not doing it right.
This blog post complements the WordCamp Vancouver 2014 Talk I gave called How to build your own robot.
I was working on a new website with a new collaborator who was literally 5,000 mile away for a client was 300 miles away. With all this long distance I’ve been using both Asana and GitHub to keep the team organized.
I wanted to but hadn’t tried to sync the commit message from GitHub to tasks in Asana. I was originally inspired by the svn-bot that appears in the WordPress core IRC chat.
While I had never set up this before both services make it quite easy.
You can set up the connection on your own Asana user account. But then all of the commits from everyone on the project will be attributed to you. What Asana support suggested was that I make a new user and call it git commit or commit. I took this one step further and gave my user the Octocat Icon. Once you have set up this user go into the account settings and grab the API Key.
The GitHub Sync is repo based and not user based and is located under the webhooks and services. Put the Asana API Key in the Auth token. You can also restrict it to just one branch if you like.
So whenever anyone commits to the repo all he have to do is grab the URL of the task from Asana and put it in the description of the GitHub commit and it will appear in Asana under the user Git Commit.
This method isn’t application specific any way you want to commit to Github will work. You can also add multiple tasks and the commit will be tracked in both tasks.
The git-bot will publish who made the commit, which branch and the account and repo name it also links back to the GitHub commit.
This really helped in both a contractor and client setting. Assigning tasks to contractors was easy and feedback on the commit as well. When the client found a bug on the beta launch of the site they recorded it on Asana and they knew when it was fixed. This really worked well in both regards as anyone involved could see the progress of the project.
The condensed workflow:
- Create / get assigned Task in Asana
- Code away upload via FTP
- Commit the code with the Asana task url in the description of the commit.
- See the commit in the Asana.
Couple side notes:
- We weren’t using any auto deployment on upload. ( FTPloy, Beanstalk, Dandelion )
- I didn’t want to track every single commit on Asana, just ones which either completed the task or which required review by another team member.
Slides from WordCamp Talk:
You’re a WordPress developer and you attend WordCamps?
But I ask you? Have you ever attended a Contributor Day?
The reason I ask is many WordCamps now are actually two-day events. First day is the general conference with speakers and the second day is a contributor day. I have attended the contributor days at WordCamp Seattle for two years now and it’s a great place to learn, talk, discuss WordPress core and how you can contribute back to WordPress. (Hence the name)
Have you working with WordPress and said:
- I wish I had time to suggest or submit an improvement to WordPress.
- I think this is a bug but I am not sure and I am way to busy at work to investigate.
- Why doesn’t the codex have updated documentation on this.
- There are a lot of unanswered questions in the forums.
These are all great reasons to go to a contributor day and give back to the community!
You’ll also be able to meet and chat with other developer and often their are core contributors or committers to WordPress in attendance that you can converse with.
So if you love WordPress and want to start contributing but don’t know where to start. Then attend a contributor day and find a way to give back.
ps. WordCamp Vancouver 2014 is holding it’s first Contributor Day and you should attend!
PC: Because @10up is distributed, Yosemite is my office today. We’re hiring. #php #css #js #WordPress pic.twitter.com/hrW0FoFVOr
RD: You weren’t looking for the OS were you?
PC: Rode through without a windshield. Still working out the bugs.
RD: I am just glad you didn’t crash exploring the new OS…
PC: I was surprised it was on a drive. Thought they switched to cloud distribution.
RD: But I bet it was a swift ride!
PC: Now that you mention it, the Dashboard did say I was going pretty fast.
RD: Was it a test drive? http://appleseed.apple.com/sp/betaprogram/
PC: All good things have to come to and end. I heard from my Notification Center.
You can read our conversation here… It was totally geeky on the fly and a little silly fun on a Wednesday Night
ps. No… neither of us work for Apple or the National Parks Service.
I call Seattle my adopted American home town because I visit it so much. My sense of direction get better each time I visit, but I still use a fuzzy logic called:
I don’t necessarily know where I am going but I certainly know when I am lost.