doc

CHANGELOG.md

@@ -1,5 +1,17 @@
 # Generic Webhook Plugin Changelog
 Changelog of Generic Webhook Plugin.
+## Unreleased
+### No issue
+**doc**
+
+[8a3d16c88f8c0b7](https://github.com/jenkinsci/generic-webhook-trigger-plugin/commit/8a3d16c88f8c0b7) Tomas Bjerre *2017-03-14 18:13:56*
+
+## 1.4
+### No issue
+**Correcting wiki link**
+
+[37694044b53d9f9](https://github.com/jenkinsci/generic-webhook-trigger-plugin/commit/37694044b53d9f9) Tomas Bjerre *2017-03-14 18:10:59*
+
 ## 1.3
 ### GitHub [#2](https://github.com/jenkinsci/generic-webhook-trigger-plugin/issues/2) Conditional trigger
 **Adding filtering option #2**

README.md

@@ -16,20 +16,7 @@ This means it can trigger on any webhook, like:
 * [Assembla](https://blog.assembla.com/AssemblaBlog/tabid/12618/bid/107614/Assembla-Bigplans-Integration-How-To.aspx)
 * An many many more!
 
-The original use case was to build merge/pull requests. This is easily done with a shell script build step.
-
-```
-git clone $PULL_REQUEST_TO_HTTP_CLONE_URL  
-cd *  
-git reset --hard $PULL_REQUEST_TO_HASH  
-git status  
-git remote add from $PULL_REQUEST_FROM_HTTP_CLONE_URL  
-git fetch from
-git merge $PULL_REQUEST_FROM_HASH  
-git --no-pager log --max-count=10 --graph --abbrev-commit
-
-#compile command here ...
-```
+The original use case was to build merge/pull requests. You may use the Git Plugin as described in [this blog post](http://bjurr.com/continuous-integration-with-gitlab-and-jenkins/) to do that. There is also an example of this on the [Violation Comments to GitLab Plugin](https://wiki.jenkins-ci.org/display/JENKINS/Violation+Comments+to+GitLab+Plugin) page.
 
 You may want to report back to the invoking system. [HTTP Request Plugin](https://wiki.jenkins-ci.org/display/JENKINS/HTTP+Request+Plugin) is a very convenient plugin for that.