We've switched to Linear, so you might be searching this card:
https://makandracards.com/makandra/620718-bookmarklet-to-generate-a-commit-message-for-an-issue-in-linear-app
We usually generate our commit messages from Pivotal Tracker IDs and titles, like
[#15775609] Index view for conflicts
The
geordi
Show archive.org snapshot
command commit automates this. (See: Pretty Commit messages via geordi).
Just run geordi commit and it will connect to PT and let you select from a list of all started and finishes stories. Then it runs git commit with the generated message (i.e. all staged changes will be commited).
When running for the first time, Geordi will request your PT token (found on your profile) and your Pivotal Tracker initials. Those information will be used to fetch data from PT and highlight your stories to spot them easily.
You need to put the PT project IDs (found in the URL at Pivotal Tracker) in a .geordi.yml file within your project directory:
pivotal_tracker_project_ids: 1234567
If you are working on a project that is fed stories from multiple Pivotal Tracker projects you can add those extra IDs to the .geordi.yml file as well. Separate them by some kind of whitespace.
pivotal_tracker_project_ids: 1234567 7654321
Dependencies are Ruby, Rubygems and the highline, yaml and pivotal-tracker gems, auto-installed by Geordi.
Note that while previously there was a file attached to this card, it's part of geordi since version 0.7.0.
