envoyproxy/envoy

RepoKitteh-based PR checklists

Open

#12,949 opened on Sep 2, 2020

View on GitHub
 (13 comments) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
area/repokittehbeginnerenhancementhelp wanted

Repository metrics

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

Description

We can have RK automatically label any change to source/ or api/ without a change to current.rst with a release-notes blocker, requiring manual confirmation from maintainers that the release notes step has been satisfied. Similarly this could work for documentation checks, i.e. validate that at least some change has happened in docs/.

I'd propose that we take the existing ownerscheck.star and add a path expression that suppresses a given check. That should be all that is needed for release notes or docs.

@envoyproxy/maintainers are there other common review checklist items that RK could help with? CC @itayd

Contributor guide

Research direction
Examine the existing ownerscheck.star file in the repository, understand how path expressions work, and add a new path suppression for release notes and docs checks.
Tech stack
None
Domain
devops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65