envoyproxy / envoyproxy/toolshed

Track upstreaming of Envoy Bazel Registry modules to BCR and source repos

Ouverte
#3,524 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
bazel-registry needs:bcr needs:upstreaming
Langage dominant
Python
Étoiles
12
Forks
24
Merge moyen
6 h 37 min
PR mergées (30 j)
92

Description

This parent issue tracks the upstreaming progress for all modules in envoyproxy/toolshed's Bazel registry. Sub-issues will be created for each module@version covering:
- Migration to Bazel Central Registry (BCR)
- Any required upstreaming to source repo (especially for MODULE.bazel changes)
- Coordination on version, overlays/patches, dependencies, and blockers
- Status and links to PRs/issues in BCR or upstream sources

**Sub-issues will include:**
- Module name & version
- BCR status (exists/needs new)
- Source repo status (overlay/needs MODULE.bazel)
- Checklist: compare toolshed and BCR, create PRs, coordinate with upstream, update envoy
- Notes on blockers/dependencies

**Use this issue for discussion, tracking status, and linking all upstreaming efforts.**

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.