GitTracker, or git-tracker, is a Git hook that will scan your current branch name looking for something it recognizes as a Pivotal Tracker story number. If it finds one, it will automagically add it, in the special format, to your commit message.

Slurper allows you to quickly compose your stories in a text file and import them into Pivotal Tracker.

We are heavy users of Pivotal Tracker here at Carbon Five, and each project evolves workflows around its use. I recently spent some time writing a Chrome extension to help support some of the common interaction patterns that come up in our workflows.

This blog post is not about that.

I started to write up a post about the Chrome extension and how I developed it (forthcoming), but realized that I needed to show screenshots. Unfortunately, I can’t use images of a client’s production tracker. Hmm.

I quickly whacked together a Ruby script to generate realistic-looking stories in a tracker project. Here it is!


github: Lorem Tracker

I have integrated Pivotal Tracker (our project management software) with Yammer (our messaging software), and now everyone on the dev team can all stay up to date with what everybody else is doing in near real-time!

GitHub with Pivotal Tracker is the killer agile combination.
With the just release Tracker v3 API update it is now easy to connect them.

You only have to configure GitHub Post-Receive Hooks so you can automatically deliver stories/bugs by providing the Tracker ID in the commit statement like: Fixes #TrackerId