[maven-release-plugin] prepare release ghprb-1.12
[maven-release-plugin] prepare for next development iteration
Create missing PR during synchronize trigger

When the GitHub syncronize trigger is sent (e.g. adding commits to a
pull request) it can fail if Jenkins didn't previously know about the
PR.  This can happen, for example, if Jenkins missed an `opened`
message, or if the PR was created before GHPRB was enabled.

This fixes this by creating the pull request if it is missing.
FIX: Broken configuration caused NPE
Storing only project name for logging purposes
Merge pull request #159 from rajish/broken-config-npe

Broken configuration causes NPE
[maven-release-plugin] prepare release ghprb-1.12
[maven-release-plugin] prepare for next development iteration
Create missing PR during synchronize trigger

When the GitHub syncronize trigger is sent (e.g. adding commits to a
pull request) it can fail if Jenkins didn't previously know about the
PR.  This can happen, for example, if Jenkins missed an `opened`
message, or if the PR was created before GHPRB was enabled.

This fixes this by creating the pull request if it is missing.
Merge pull request #30 from blt04/pull-request-missing

Create missing PR during synchronize trigger
Add FINEST debugging and fix #153
Update README with info regarding non-PR refspec

Using the default `refspec` prohibits the project from automatically building non-PR branches like `origin/master`. Prepending the `refspec` with the heads and remote/origin allows the project to build pull requests as well as other branches like `origin/my-feature`. This should resolve #77.

Big thanks to https://github.com/janinko/ghprb/issues/77#issuecomment-40400379 :smile:
Merge pull request #168 from justindowning/patch-1

Update README with info regarding non-PR refspec
Merge pull request #166 from nocturo/bugfix/triggeronly

Add FINEST debugging and fix #153
Set the the value of GIT_BRANCH when kicking off builds