Add a workflow that dismisses stale reviews - if a reviewer approved a PR, then the PR changed, but not the CODEOWNER's file, then that CODEOWNER's approval is still effective.
Motivation
The following scenario happened a few times:
We (integration-platform) have a PR for this repo.
Agent-integrations (CODEOWNER) approves the PR.
Some files changed in this PR.
Agent-integrations is not the CODEOWNER for those files. But now the approval is staled. We have to ask for approval again.
With this change, step 4 is not needed, lowering the workload of agent-integrations and speeding up the turnaround timeframe.
Additional Notes
N/A.
Review checklist (to be filled by reviewers)
[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged
What does this PR do?
Add a workflow that dismisses stale reviews - if a reviewer approved a PR, then the PR changed, but not the CODEOWNER's file, then that CODEOWNER's approval is still effective.
Motivation
The following scenario happened a few times:
With this change, step 4 is not needed, lowering the workload of agent-integrations and speeding up the turnaround timeframe.
Additional Notes
N/A.
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged