Pretty commit messages via geordi

Posted Over 5 years ago. Visible to the public. Repeats.

Geordi Show archive.org snapshot provides a pretty neat way to generate beautiful commit messages according to your stories in Pivotal Tracker Show archive.org snapshot :

geordi commit

Geordi reads from a .geordi.yml file inside your repo and connects to Pivotal Tracker to list started and finished stories with their title. Choosing one of them generates a commit message including id and title from pivotal tracker. For example:

[#1234567] CRUD Users

Trouble shooting

If you encounter a bug like 401 Unauthorized (RestClient::Unauthorized) your API token probably changed.

Check if your API token differs from the one configured for geordi:

  • In Pivotal Tracker you can find your API token in your Profile Information.
  • Geordi uses the one configured in ~/.config/geordi/global.yml (previously ~/.gitpt)

If they don't match, replace the API token with the one from Pivotal Tracker.

Natalie Zeumann
Say thanks2
Last edit
Over 3 years ago
Dominik Schöler
License
Source code in this card is licensed under the MIT License.

Related cards:

Change commit messages of past Git commits

To change a commit message of the most recent (unpushed) commit, you can simply use
git commit --amend -m 'new message'

To change messages of (unpushed) commits further in the past:

git rebase -i [COMMIT BEFORE THE FIRST YOU WANT TO ...

Squashing several Git commits into a single commit

This note shows how to merge an ugly feature branch with multiple dirty WIP commits back into the master as one pretty commit.

Squashing commits with git rebase

What we are describing here will destroy commi...

Shell script to generate a Git commit with Pivotal Tracker story ID and title

We usually generate our commit messages from Pivotal Tracker IDs and titles, like
[#15775609] Index view for conflicts

The geordi command commit automates this. (See: [Pretty Commit messages via geord...

Improved gitpt now part of geordi

Our gitpt script to generate git commits from Pivotal Tracker stories has been tweaked and polished and is now part of the [...

Git: Changing commit messages

To change the commit message of the latest (unpushed, unmerged) commit, you can use
git commit --amend

To change the commit message of an earlier (unpushed, unmerged) commit [COMMIT], you can do
git rebase -i COMMIT~

For a current versio...

Git: Revert one or more commits

Reverting a commit means creating a new commit that undoes the old changes.

Imagine the following commit history:

* commit_sha3 [Story-ID 1] Fixup for my feature 
* commit_sha2 [Story-ID 5] Other feature
* commit_sha1 [Story-ID 1] My fea...

Git: Change author of a commit

Using git rebase can be painful but luckily you can resort to cheating with git reset and committing anew.
Now what if you wanted to rebase commits of ot...

Git: Change the text editor used to enter commit messages

In your ~/.gitconfig:

[core]
  editor=nano

Deployment: Merge consecutive commits without cherry-picking

You want to deploy new features but the latest commits are not ready for production? Then use git merge master~n to skip the n-last commits.

Tip

A big advantage of merging vs. cherry-picking is that cherry-picking will create copies o...

Git: See all unpushed commits or commits that are not in another branch

If you need to find out which of your local commits are not on the remote server do this:

git cherry -v

The -v option prints out the commit messages. Without it you will see only the SHA1 codes.

You may also compare against another (upstr...

Posted by Natalie Zeumann to makandra dev (2018-08-20 12:46)
This website uses short-lived cookies to improve usability.
or learn more