When the user triggers a pipeline run via a web-hook, pipeline runs continue to get generated because the event-type of the webhook is too generic. A new pipeline run gets triggered because the pipeline run has a task that is responsible for creating releases on the same repository. And a new Github release by definition is a push
This issue has been resolved by creating another repository such as pipeline-server to host your default-kabanero-pipelines.tar.gz refer to https://github.com/oiricaud/pipeline-server/releases for an overview
When the user triggers a pipeline run via a web-hook, pipeline runs continue to get generated because the event-type of the webhook is too generic. A new pipeline run gets triggered because the pipeline run has a task that is responsible for creating releases on the same repository. And a new Github release by definition is a push