Added foo.
Close DOCTORS-250 #resolved #fixed
Revert accidentally commited test file while exploring a new commit message structure.
Create composite commit message with information from both the jira issue and the git log for feature finishing merge commits, along with some string formatting functions.
Use new commit message in git-issue-finish.
Bump version number to 0.3.4.
Subcommit(s):
Hopefully fix string unquoting issues.
Resolved Issue DEV-63: Create Better Commit Message For Git Jira Flow

  The commit messages that are generated and attached to the merge commit when
  calling "git issue finish" need to be more informative.  I propose that they
  are multi-line, and not only contain the Issue Key for the "Smart Commits"
  system, but also the summary and description from the issue in question, as
  well as the user-created commit message(s) from the commit(s) on the issue
  branch.  It should look something like: Resolved Issue DEV-1000: Tool To Read
  Someone's Mind Create a tool that is able to read someone's mind and generate
  an issue that solves their problem exactly to their expectations.  The tool
  should also be able to generate the relevant code necessary to resolve the
  issue, implement it into the project, commit it into the repository, and
  update said issue status automatically.  Relaxing temple massage for the
  assigned developer should be optional.  Sub Commit(s): 02d99ff Created a
  self-aware software heuristic.  7cfd7ca Hired Ray Kurzweil to manage.  The git
  command to collect the commits from the issue branch is: $ git log
  <branch_name> --not HEAD --oneline For some reason, it needs to be run after
  switching by to the development branch, but (of course) before merging.

Subcommit(s):
  d6a0d2b Hopefully fix string unquoting issues.
Fix type keeping jira issue key from displaying in commit message.
Resolved Issue DEV-63: Create Better Commit Message For Git Jira Flow

  The commit messages that are generated and attached to the merge commit when
  calling "git issue finish" need to be more informative.  I propose that they
  are multi-line, and not only contain the Issue Key for the "Smart Commits"
  system, but also the summary and description from the issue in question, as
  well as the user-created commit message(s) from the commit(s) on the issue
  branch.  It should look something like: Resolved Issue DEV-1000: Tool To Read
  Someone's Mind Create a tool that is able to read someone's mind and generate
  an issue that solves their problem exactly to their expectations.  The tool
  should also be able to generate the relevant code necessary to resolve the
  issue, implement it into the project, commit it into the repository, and
  update said issue status automatically.  Relaxing temple massage for the
  assigned developer should be optional.  Sub Commit(s): 02d99ff Created a
  self-aware software heuristic.  7cfd7ca Hired Ray Kurzweil to manage.  The git
  command to collect the commits from the issue branch is: $ git log
  <branch_name> --not HEAD --oneline For some reason, it needs to be run after
  switching by to the development branch, but (of course) before merging.

Subcommit(s):
  9b962fd Fix type keeping jira issue key from displaying in commit message.
Fix issue description indentation and bump version release per DEV-65.
Resolved Issue DEV-63: Create Better Commit Message For Git Jira Flow

The commit messages that are generated and attached to the merge commit
when calling "git issue finish" need to be more informative.  I propose
that they are multi-line, and not only contain the Issue Key for the
"Smart Commits" system, but also the summary and description from the
issue in question, as well as the user-created commit message(s) from
the commit(s) on the issue branch.  It should look something like:
Resolved Issue DEV-1000: Tool To Read Someone's Mind Create a tool that
is able to read someone's mind and generate an issue that solves their
problem exactly to their expectations.  The tool should also be able to
generate the relevant code necessary to resolve the issue, implement it
into the project, commit it into the repository, and update said issue
status automatically.  Relaxing temple massage for the assigned
developer should be optional.  Sub Commit(s): 02d99ff Created a
self-aware software heuristic.  7cfd7ca Hired Ray Kurzweil to manage.
The git command to collect the commits from the issue branch is: $ git
log <branch_name> --not HEAD --oneline For some reason, it needs to be
run after switching by to the development branch, but (of course) before
merging.

Subcommit(s):
  2df36dc Fix issue description indentation and bump version release per
  DEV-65.
Merge pull request #1 from localmed/development

Development