I'd like to have a report of the PR staleness overtime, e.g. the longest time of last PR activity, and see how that will change over time.
For example, I can manually extract this information from my daily report. For example, on Feb 12 2019, the stalest is 2month. However, on Feb 14th, the stalest is only 2 days. Where people start to sweep the old PRs and triage on the release schedule. That's a new process, but just onetime effort.
Our situation is that we usually have PR left unattended too long, and accumulate over time, and become a technical debt to deal with, and also usually a long stale PR is an indication of communication gap, and we need to find that pattern and start to address those gaps.
Current reports only give me the PR review turnaround (from review requested to answered) time, but I am looking for just the PR staleness, e.g. anybody can respond to a PR without being requested.
The goal is to encourage shared ownership, better community engagement, reduced feedback loop, and higher developer satisfaction. Thanks.
I'd like to have a report of the PR staleness overtime, e.g. the longest time of last PR activity, and see how that will change over time.
For example, I can manually extract this information from my daily report. For example, on Feb 12 2019, the stalest is 2month. However, on Feb 14th, the stalest is only 2 days. Where people start to sweep the old PRs and triage on the release schedule. That's a new process, but just onetime effort.
Our situation is that we usually have PR left unattended too long, and accumulate over time, and become a technical debt to deal with, and also usually a long stale PR is an indication of communication gap, and we need to find that pattern and start to address those gaps.
Current reports only give me the PR review turnaround (from review requested to answered) time, but I am looking for just the PR staleness, e.g. anybody can respond to a PR without being requested.
The goal is to encourage shared ownership, better community engagement, reduced feedback loop, and higher developer satisfaction. Thanks.