envoyproxy/envoy

Automatically assign @envoyproxy/stable-maintainers to backports

Open

#10,049 opened on Feb 13, 2020

View on GitHub
 (6 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/communityhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

@envoyproxy/stable-maintainers (or only stable release manager, but I don't believe we have a separate group for that?) should be automatically assigned all PRs sent against release/vX.Y branches.

We could achieve this either by: a) Replacing CODEOWNERS with * @envoyproxy/stable-maintainers, but it doesn't look like CODEOWNERS are automatically assigned changes in the release/vX.Y branches right now. b) Make @repokitteh auto-assign @envoyproxy/stable-maintainers for those PRs, similarly to how it auto-assigns @envoyproxy/api-shepherds for the api/ changes.

@mattklein123 any thoughts and/or preference?

Contributor guide

Research direction
Investigate how to configure CODEOWNERS for release branches or set up repokitteh to auto assign stable maintainers.
Tech stack
github actions
Domain
devops
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitHubCODEOWNERS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25