devcontainers / devcontainers/ci
Use pattern matching in refFilterForPush
- Vorherrschende Sprache
- TypeScript
- Sterne
- 496
- Forks
- 101
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
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*
```
Beitragsleitfaden
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- github-actions, typescript
- Bereich
- ci-cd
- Issue-Typ
- Feature
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Aktiv
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 55/100