devcontainers / devcontainers/ci
Use pattern matching in refFilterForPush
- Lingua principale
- TypeScript
- Stelle
- 496
- Fork
- 101
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
One popular branching strategy, when dealing with maintenance/patch releases, is to late-cut branches. That is, you end up with something like:
```
- main
- releases/v1
- releases/v1.4
- releases/v2
- etc
```
There may or may not be a floating major/minor release branch, depending on whether there are any bug fixes for any particular released version.
The problem is that currently `refFilterForPush` would require listing all such branches explicitly, meaning modifications to CI scripts for each release.
Instead, it would be nice if `refFilterForPush` supported pattern matching/globbing:
```yaml
- name: Pre-build dev container image
uses: devcontainers/ci@v0.3
timeout-minutes: 10
with:
imageName: someRepo/someImage
imageTag: sometag
subFolder: src
push: filter
refFilterForPush: |
refs/heads/main
refs/heads/releases/v*
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start with the refFilterForPush entry point and the YAML example in the issue. Confirm how exact refs are currently selected, then define and verify matching for refs/heads/main and refs/heads/releases/v* so release branches do not need to be listed individually.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- github-actions, typescript
- Ambito
- ci-cd
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 55/100