You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came across https://arxiv.org/abs/2304.08426 which analyses the human and bot response time to PRs, and it talks specifically about the factors that cause a PR to be open for a longer time.
It finds that human responses are the major factor in PR lifetime, relative to bots that respond quickly, but don't change the PR's reception by that much.
One thing mentioned is that in most cases, delays were not explained. Where that could be due to the size of the patch, code freeze, any number of reasons. Might be some useful advice there for folks responding to these delayed PRs. E.g. how can we advise authors to clean up a PR that might have a confusing description, or too many individual commits, etc.
It would be great for a bot to detect PRs, especially by newcomers, who haven't gotten a reaction.
The bot should:
The text was updated successfully, but these errors were encountered: