envoyproxy/envoy

Don't block api/ changes in the stable release branches

Open

#10,035 opened on Feb 12, 2020

View on GitHub
 (0 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

@repokitteh shouldn't add api label and request review from @envoyproxy/api-shepherds for the api/ changes on the stable release branches, since those changes were already approved on the master branch.

cc @itayd @mattklein123

Contributor guide

Research direction
Locate the repokitteh configuration (likely in .github/ or a separate repo) that triggers the api label addition on PRs, and modify it to skip stable release branches by checking branch name patterns.
Tech stack
None
Domain
devopsci cd
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50