-
Notifications
You must be signed in to change notification settings - Fork 35.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
script: update REVIEWERS #21823
script: update REVIEWERS #21823
Conversation
Tagging @adamjonas added as author. |
Feel free to add below Descriptors:
And somewhere else:
(maybe use *_compatibility.py for the first two lines) |
It wasn't clear to me whether people liked what DrahtBot does, so I am not running it 24/7. Since people are still happily adding themselves to the list, I presume I should run it more often? |
I don't mind getting a notification, though it might be annoying for copyright year changes and stuff like that. |
@Sjors nice; updated. |
Sure, but this change should only happen once a year per file. Though, it is currently unclear if the listed reviewers want to be notified about refactoring changes of the listed files. |
Maybe sending review notifications a couple of times a week would be a good frequency, as a suggestion. |
Re-opening, sorry, crossed signals. |
ACK 48bd9eb: patch looks correct :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 48bd9eb, I have reviewed the code and it looks OK, I agree it can be merged.
Glad to hear people still want this. ACK 48bd9eb. I ran through the new files added with |
48bd9eb script: update REVIEWERS (Adam Jonas) Pull request description: Meta: `git show a06eb03` indicates the commit was first made one year ago and the PR was merged in September 2020. It might be time for an update, if automated review requests via DrahtBot are operational. "Regular contributors are free to add their names to specific directories or files provided that they are willing to provide a review." Perhaps we can compile and squash suggested updates here, per that guideline. ACKs for top commit: practicalswift: ACK 48bd9eb: patch looks correct :) adamjonas: ACK 48bd9eb. I ran through the new files added with `*`s using `git ls-files`. hebasto: ACK 48bd9eb, I have reviewed the code and it looks OK, I agree it can be merged. Tree-SHA512: 770fd60d78bd64100814c72211e4bd97718c87a55a4c91e136fababa0149d12cdc1b3e89462dee3a55e5f51d3263420cc6d856868469eb9a72ff8c930859c54f
48bd9eb script: update REVIEWERS (Adam Jonas) Pull request description: Meta: `git show a06eb03` indicates the commit was first made one year ago and the PR was merged in September 2020. It might be time for an update, if automated review requests via DrahtBot are operational. "Regular contributors are free to add their names to specific directories or files provided that they are willing to provide a review." Perhaps we can compile and squash suggested updates here, per that guideline. ACKs for top commit: practicalswift: ACK 48bd9eb: patch looks correct :) adamjonas: ACK 48bd9eb. I ran through the new files added with `*`s using `git ls-files`. hebasto: ACK 48bd9eb, I have reviewed the code and it looks OK, I agree it can be merged. Tree-SHA512: 770fd60d78bd64100814c72211e4bd97718c87a55a4c91e136fababa0149d12cdc1b3e89462dee3a55e5f51d3263420cc6d856868469eb9a72ff8c930859c54f
48bd9eb script: update REVIEWERS (Adam Jonas) Pull request description: Meta: `git show a06eb03` indicates the commit was first made one year ago and the PR was merged in September 2020. It might be time for an update, if automated review requests via DrahtBot are operational. "Regular contributors are free to add their names to specific directories or files provided that they are willing to provide a review." Perhaps we can compile and squash suggested updates here, per that guideline. ACKs for top commit: practicalswift: ACK 48bd9eb: patch looks correct :) adamjonas: ACK 48bd9eb. I ran through the new files added with `*`s using `git ls-files`. hebasto: ACK 48bd9eb, I have reviewed the code and it looks OK, I agree it can be merged. Tree-SHA512: 770fd60d78bd64100814c72211e4bd97718c87a55a4c91e136fababa0149d12cdc1b3e89462dee3a55e5f51d3263420cc6d856868469eb9a72ff8c930859c54f
48bd9eb script: update REVIEWERS (Adam Jonas) Pull request description: Meta: `git show a06eb03` indicates the commit was first made one year ago and the PR was merged in September 2020. It might be time for an update, if automated review requests via DrahtBot are operational. "Regular contributors are free to add their names to specific directories or files provided that they are willing to provide a review." Perhaps we can compile and squash suggested updates here, per that guideline. ACKs for top commit: practicalswift: ACK 48bd9eb: patch looks correct :) adamjonas: ACK 48bd9eb. I ran through the new files added with `*`s using `git ls-files`. hebasto: ACK 48bd9eb, I have reviewed the code and it looks OK, I agree it can be merged. Tree-SHA512: 770fd60d78bd64100814c72211e4bd97718c87a55a4c91e136fababa0149d12cdc1b3e89462dee3a55e5f51d3263420cc6d856868469eb9a72ff8c930859c54f
48bd9eb script: update REVIEWERS (Adam Jonas) Pull request description: Meta: `git show a06eb03` indicates the commit was first made one year ago and the PR was merged in September 2020. It might be time for an update, if automated review requests via DrahtBot are operational. "Regular contributors are free to add their names to specific directories or files provided that they are willing to provide a review." Perhaps we can compile and squash suggested updates here, per that guideline. ACKs for top commit: practicalswift: ACK 48bd9eb: patch looks correct :) adamjonas: ACK 48bd9eb. I ran through the new files added with `*`s using `git ls-files`. hebasto: ACK 48bd9eb, I have reviewed the code and it looks OK, I agree it can be merged. Tree-SHA512: 770fd60d78bd64100814c72211e4bd97718c87a55a4c91e136fababa0149d12cdc1b3e89462dee3a55e5f51d3263420cc6d856868469eb9a72ff8c930859c54f
Meta:
git show a06eb03
indicates the commit was first made one year ago and the PR was merged in September 2020.It might be time for an update, if automated review requests via DrahtBot are operational.
"Regular contributors are free to add their names to specific directories or files provided that they are willing to provide a review."
Perhaps we can compile and squash suggested updates here, per that guideline.