Could we just use the same set of reviewers as pr-bot in the main repo [1]? I don't think that we could avoid duplicating the data though.
[1] https://github.com/apache/beam/blob/728e8ecc8a40d3d578ada7773b77eca2b3c68d03/.github/REVIEWERS.yml On Thu, Oct 27, 2022 at 12:20 PM David Cavazos via dev <dev@beam.apache.org> wrote: > Hi everyone! > > We want to make sure the Beam starter projects always come with the latest > (compatible) versions for every dependency. I enabled Dependabot on all of > them to automate this as much as possible, and we have automated tests to > make sure everything works as expected. > > However, we still need someone to merge Dependabot's PRs. The good news is > that since the starter projects are so simple, if tests pass they're most > likely safe to merge, and tests only take a couple minutes to run. > > We could either batch update all dependencies as part of the release > process, or have people check them periodically (like an owner per > language). > > These are all the repos we have to keep an eye to: > > - https://github.com/apache/beam-starter-java -- 9 updates, all tests > passing > - https://github.com/apache/beam-starter-python -- 2 updates, all > tests passing > - https://github.com/apache/beam-starter-go -- 0 updates > - https://github.com/apache/beam-starter-kotlin -- 3 updates, all > tests passing > - https://github.com/apache/beam-starter-scala -- not done yet, but > keep an eye > >
