What

PR Gatekeeper can accept different approve-config.yml files based on the source & target branch being merged. In multi-stage branching/ approval workflows, there may be multiple contexts where PR Gatekeeper is run.

But

When we have more than 1 Open Pull Request using PR Gatekeeper, the PR Gatekeeper Status reflects the status message from the more recently raised/ run PR.

And

This behaviour is confusing to the reviewers of the prior PRs, and the PR Gatekeeper Status needs to be unique per PR

So

Fixing this, will help us leverage PR gatekeeper's features in multi-stage approval workflows.