damccorm opened a new pull request #16984:
URL: https://github.com/apache/beam/pull/16984


   Right now, we don't have a well defined automated system for staying on top 
of pull request reviews - we rely on contributors being able to find the 
correct OWNERS file and committers manually triaging/calling attention to old 
pull requests. This is the continuation of an effort to improve our automation 
around this. [Design doc for the full effort 
here](https://docs.google.com/document/d/1FhRPRD6VXkYlLAPhNfZB7y2Yese2FCWBzjx67d3TjBo/edit#).
   
   This specific change turns on the bot for changes to the Go Sdk - it 
shouldn't have any impact on other sdks. It builds off of the most recent set 
of changes in #16898. This code is mirrored here - 
https://github.com/damccorm/beam-pr-bot-demo - you can see see the completed 
portions of the bot in action in [the prs in that 
repo](https://github.com/damccorm/beam-pr-bot-demo/pulls) (they show different 
use cases and exercise almost all of the behavior of the bot).
   
   **Next Steps**
   
   Initially, I am filtering all bot activity prs with the Go label. This is to 
minimize the blast radius of the automation in case it doesn't work perfectly 
out the gate or we find it unhelpful. Eventually, I plan on expanding to the 
rest of the repo.
   
   I also plan on adding some more p2 functionality. This includes:
   
   - A script to gather metrics to measure the bots effectiveness (comparing it 
to historical data)
   - Flagging/updating reviewers for stale review requests
   - Automatically updating our reviewer config to incorporate new reviewers
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [ ] [**Choose 
reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and 
mention them in a comment (`R: @username`).
    - [x] Format the pull request title like `[BEAM-XXX] Fixes bug in 
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA 
issue, if applicable. This will automatically link the pull request to the 
issue.
    - [ ] Update `CHANGES.md` with noteworthy changes.
    - [x] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://beam.apache.org/contribute/#make-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/workflows/Build%20python%20source%20distribution%20and%20wheels/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/workflows/Python%20tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/workflows/Java%20Tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to