« Back to Planio Blog 8ed42c1ac769b0246bad7f1a0a750b35
Thomas Carney
Thomas thinks of ways to make Planio grow, writes content and ponders metrics.
September 29, 2015 · 1 min read

Use Git Commit Messages to Improve Your Planio Workflow

Git is tightly integrated into Planio. You can manually link a Git commit to an issue in Planio in the repository viewer.

You might want to avoid this duplication of effort and save some time.

You can reference particular issues, update issue statuses and even log time all from Git commit messages from the command line.

Referencing Git Commits in Planio Issues

For example:

git commit -m “adds Schnitzel finder beacon ref #1123”

The #1123 is the number you’ll find in the header when you’re looking at an issue.

For example, in the case of the issue below, the number of the issue is #1123.

When you push that commit to the repository in Planio, you’ll be able to see a link to the commit under “Associated Revisions” when you view issue #1123.

image

You can then discuss the commit, make comments on the quality of the code and so forth.

Update Issue Status

You can also update the status of the issue right in the commit message.

git commit -m “refactored Schnitzel found beacon closes #1123”

The status of the issue will be set to “closed”.

Obviously, you’d like to customize this with your own keywords and statuses. Go to Administration -> Settings -> Repositories, where you can define keywords along with statuses.

This is handy for moving an issue through your development process from ‘development’ status to ‘QA’ status and so on.

For example, you could set up Planio so the following commit messages moves an issue from the “development” status to the “QA” status

git commit -m “fixes beacon size problem QA #1123”

Time Logging

You can can log time on an issue right in the commit message as well.

For example, taking one of the Git commits from above, you could log 2.5 hours of work like this:

git commit -m “adds Schnitzel found beacon ref #1123 @2.5”

You’ve just logged 2.5 hours on issue number #1123.

And that’s pretty much it!

comments powered by Disqus