This is hard to answer in detail as for me some more context is missing. In general I'd say it first of all makes sense to not trigger the Jenkins pipeline on PR approval (or decline). Question remains thought why you might think otherwise - or did I read that wrong?
This is my understanding:
Approving a pull-request does not change the contents/scope of the pull-request which is why there is no need to run the Jenkins pipeline again - it did already run on that revision.
Your mileage may vary thought. If you share a bit more of the context and what your motivation is, it might be possible to give better feedback and propose some more options.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.