Skip to content

Releases: mezis/git-whistles

v1.0.2

23 Jan 18:02
Compare
Choose a tag to compare
Bugfix

Previous version was not compatible with latest rubygems update causing the gem to fail to install. In this version, the gem was compiled with ruby 2.2.4 and then pushed to rubygems. It should now be installable under all recent rubygems versions.

v1.0.1

22 Jan 16:20
Compare
Choose a tag to compare
Breaking change
  • git-pull-request as been renamed as git-pivotal-pr. This was done in order to not clash with hub gem. Thanks to @jphastings for his contribution.
Improvements
  • When pulling the description body from Pivotal Tracker using git-pull-request sometimes we would hit a GET request limit and Github would raise a 414. We now check how many bytes the description has and warn the user via the CLI if the description is too long. We then print to STDOUT the story description that can be copy / pasted into the PR.
  • When the Pivotal Tracker auth token is invalid, the REST client no longer raises an Authentication exception, instead we print to the STDOUT a warning to the user.
  • We have added git-jira-branch which behaves similar to git-pivotal-branch. As the name implies it will try to search in JIRA for the issue id. Please check the README for more information on this. Thanks for @martyphee for his contribution.
Bugfixes
  • We have squashed some whitespace handling / improved merge-po functionality thanks to @Arthur2e5

v0.10.0

02 Sep 09:26
Compare
Choose a tag to compare
Improvements
  • git pivotal-open opens the Pivotal Tracker story page for the current branch, from the specified Pivotal Tracker story ID or it is inferred from the branch name if not supplied [Khiet]
  • git pull-request now asks users to complement information retrieved from pivotal tracker [Jesper]

v0.9.1

07 Jan 09:32
Compare
Choose a tag to compare
Bugfixes
  • On 0.8.0 release it was introduced --first-parent flag on git outstanding-features to prevent showing branches that were merged first into other branches (like integration branches). However if you run into this case:

    
                                          branchB
                       integrationBranch /--------\   
             branchA  /                             \
    master /------------------------------------------\-----------
    
    • Where a branch forked from master, is promoted to an integration branch, which then gets several stories merged in and finally the integration branch hits master, the integration branch wouldn't show up in the output of git outstanding-features because it was not directly forked from master (his ancestor was).

    This release reverts the use of --first-parent to avoid omitting incorrectly branch names, and will bring back all descendent PR merges.

v0.9.0

01 Jan 19:38
Compare
Choose a tag to compare
Features
  • git explore [-r ref] [-p path] opens the specific path on the given reference on GitHub website. By default opens on the root of the current branch

    Ref can be any commit SHA, branch, etc..

    Path can be folder or file

    Use cases:

    • Open a specific file in any branch from the command line
    • Open a specific file in a specific sha
    • Send easily to a coworker a link to a resource
    • Etc..

v0.8.2

17 Dec 09:58
Compare
Choose a tag to compare
Improvements
  • git latest-pushes now allows partial matching. Before this was relying on "pattern" flag for git for-each-ref however which only allowed matching branch names between slashes.

    Eg.:
    Assuming a remote branch name called: refs/remotes/origin/foo-branch/

    git latest-pushes -p foo # no match
    git latest-pushes -p foo-branch # matches

    This now keeps the same API as before (-p pattern) but allows partial matching so -p foo and -f foo-branch both yield the same results for the previous scenario

Bugfixes
  • Fixes the regexp on git outstanding-features that was chopping branches that contained the word "from".

v0.8.1

20 Nov 20:26
Compare
Choose a tag to compare
Bugfixes
  • git outstanding-features no longer chops the prefix of the branch name and should keep origin name. Also it forces the log to be output in one line so it bypasses any custom user configuration

v0.8.0

17 Nov 13:47
Compare
Choose a tag to compare
Improvements
  • git chop now supports multiple branches as arguments [Davidslv]
  • git outstanding-features now only shows first parent merges [pedrocunha]
Bugfixes
  • Fixes installation on ruby 1.8 environments [tadejm]

v0.7.7

17 Nov 13:28
Compare
Choose a tag to compare
Bugfixes
  • git pivotal-branch was incorrectly using a git checkout alias

v0.7.6

17 Nov 13:33
Compare
Choose a tag to compare
Bugfixes
  • Added license to gemspec