envoyproxy/envoy

Clarify/document repokitteh retest commands

Open

#13,351 opened on Oct 1, 2020

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

description

atm, you need to be an "approver" to trigger a retest via repokitteh

it would be helpful if the circle was widened, so regular contributors can also trigger this

not being able to trigger it means doing "empty" or "amend" commits which triggers full re-runs, and a lot of unnecessarily wasted CI cycles

Contributor guide

Research direction
Investigate the current repokitteh permissions configuration in the repository settings or CI workflow files. Identify where the 'approver' role is defined and explore how to add a new role for regular contributors. Check for any existing documentation on repokitteh commands and propose updates to include the new permission scope.
Tech stack
None
Domain
backendinfrastructure
Issue type
Documentation
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.
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
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80