Description
Users are not always inclined to study the doc. Having submitted a change it is not always obvious what to do next if there are some email exchanges and possibly new /submitted changes. This can cause changes to linger that would otherwise be ready to be integrated. It would be helpful to notify users an action may be required on their part to move a patch forward. Automated posting of a comment on 'quiet' PRs with suggestions could be useful. When a patch is ready to move forward after some exchanges and updates, the Git maintainer needs to be notified. A command to do this would be helpful (ie /mergeready, /ready2merge, /mergable, ...?).
PR #410 has the initial discussion of this issue. Something like actions/stale does some of the work. There may be other workflows providing more features.