envoyproxy / envoyproxy/envoy

[RFC] Improve PR/CI <> `git log` workflow

Open
#18,781 3 comments 0 reactions 1 assignee Claimed by @phlax View on GitHub
enhancement no stalebot
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
437

Description

### description

there have been some questions around the CI <> git log workflow, and how we might automate this

this is a tracking ticket to get some ideas on how this could be achieved

ideally suggestions should address

- what information should be stored in the `git log` and why
- my own feeling is that parsimony is valuable here
- for PRs
- what information should be stored on a PR
- how the information should be structured
- who can add any salient information
- automation/triggers according to eg tags or comments

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.