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