Skip to content

@arzzen arzzen released this Oct 27, 2019

  • #82 checkUtils: remove repeating commands
Assets 2

@arzzen arzzen released this Oct 13, 2019 · 3 commits to master since this release

  • [#80] #70 Include contribution by co-authors (Co-authored-by) in the commitsPerAuthor option.
  • [#81] #68 Fix travis-ci build on any pull request
Assets 2

@arzzen arzzen released this Aug 13, 2019 · 15 commits to master since this release

  • [#72] Update Makefile: make Use DESTDIR
Assets 2

@tomice tomice released this May 26, 2019 · 19 commits to master since this release

  • The main feature of this commit is addressing the feature request
    of adding the ability to save the output as a file to use in other
    tools. I decided to use the JSON format as it's relatively straight
    forward and easy to create thanks to a few Google searches.

    The original feature request was to add the ability to output any of
    the options as a JSON/XML/YAML format. That said, because this entire project
    is relying only on built-in shell utilities, we kind of have to format stuff
    ourselves in relatively primitive tools such as awk, sed, and bash in order
    to adhere to the "spirit" of this codebase.

    It is possible to use Perl and/or Python, but that would defeat the purpose
    of this, in my opinion. The downside of not using these tools is that it
    might not be as robust and battle hardened as the others.

    AS SUCH, THIS FEATURE IS CURRENTLY EXPERIMENTAL.

    As people provide feedback, we can adjust this and possibly extend it to
    more options. For now, it respects _GIT_SINCE and _GIT_UNTIL. It does not
    respect variable expansion in paths, though, so saving it to a location such
    as "${my_save_location}" will fail.

  • Made some of the variables a bit more robust by utilizing the -r flag to
    make the variables readonly. It should be noted that "local readonly" does
    not work, nor does "readonly local". The best way to do this is either via
    "local -r foo=bar" or "local foo=bar && readonly bar".

  • Fixed a few comments describing how functions work.

  • Added a .gitignore.

  • Changed all functions to adhere to camelCase style for no real reason
    other than consistency and a few other minor things.

  • The GPG settings don't play well with OS X if you don't have
    certain tools installed, so they were removed from the git log
    format settings for the JSON output.

  • Pictures have been updated to reflect the new menu option.

  • Closes #31

Assets 2

@tomice tomice released this May 13, 2019 · 25 commits to master since this release

#65 Improves the colors for the interactive menu

  • Legacy menu colors still available for those who prefer them
Assets 2

@tomice tomice released this May 10, 2019 · 31 commits to master since this release

#67 Add detailed git stats for a specific branch

Assets 2

@arzzen arzzen released this Feb 19, 2019 · 45 commits to master since this release

  • [#63] #62 Some months not displayed
Assets 2

@arzzen arzzen released this Feb 4, 2019 · 48 commits to master since this release

  • refs [#60]: Makefile improvements. Allowing install/uninstall as a regular (non root) user.
Assets 2

@arzzen arzzen released this Feb 2, 2019 · 56 commits to master since this release

  • All internal functions now have documentation describing what they are,
    what arguments they take, and what external variables are set in an effort
    to help others understand the codebase more quickly
  • Changed a few lines where grep | wc -l occurred, as grep has a built-in
    option to do this: grep -c
  • Removed a $* where the suggestReviewers function expected a string but
    never received one during the life of the program
  • Adjusted some lines so they weren't quite as long, adjusted some variable
    names, and other minor cleanup
Assets 2

@arzzen arzzen released this Jan 17, 2019 · 59 commits to master since this release

  • [#52] When someone has the showSignature=true flag set in their .gitconfig
    file, gpg verifying signature related text would be parsed as if it
    was actual log information. This change ignores signature-related text
    by passing the -c log.showSignature=false option to git so it ignores
    a user's custom .gitconfig showSignature flag regardless as to what it
    is set to.
Assets 2
You can’t perform that action at this time.