When reviewing new packages or updates, people tend to approve the changes proposed without adding the appropriate labels.
Nixpkgs has approvals: 1, approvals: 2, approvals: 3+ and approved-by: package-maintainer but they are still updated, manually by kind volunteers.
I think this process could be entirely automated through a small GitHub action, and I am surprised that it hasn't been yet.
In the action doc, there is an example about running a workflow when a pr review is submitted.
I also found this action that counts the number of PR approvals and this post featuring manual scripts.
This would save time and help filter the pull requests to merge them more quickly.
Issue description
When reviewing new packages or updates, people tend to approve the changes proposed without adding the appropriate labels. Nixpkgs has
approvals: 1
,approvals: 2
,approvals: 3+
andapproved-by: package-maintainer
but they are still updated, manually by kind volunteers.I think this process could be entirely automated through a small GitHub action, and I am surprised that it hasn't been yet. In the action doc, there is an example about running a workflow when a pr review is submitted.
I also found this action that counts the number of PR approvals and this post featuring manual scripts.
This would save time and help filter the pull requests to merge them more quickly.