devcontainers / devcontainers/ci
Add a boolean output to indicate if the image was pushed
- Lingua principale
- TypeScript
- Stelle
- 496
- Fork
- 101
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Please add an output that indicates whether or not the image was successfully pushed.
This can be useful in cases where the push may be filtered out, and rather than repeating the same filter on a subsequent step it would be simpler to condition it based on the output from this action. For example:
```yaml
- id: build
name: Pre-build dev container image
uses: devcontainers/ci@v0.3
with:
imageName: someRepo/someImage
imageTag: someTag
push: filter
refFilterForPush: |
refs/heads/main
- id: get-digest
name: Get image Digest
run: |
digest=$(docker inspect --format={{.Id}} someRepo/someImage:someTag
echo "Image Digest: $digest"
echo "digest=${digest}" >> $GITHUB_OUTPUT
- id: attest
name: Attest
uses: actions/attest-build-provenance@v3
with:
subject-name: someRepo/someImage
subject-digest: ${{ steps.get-digest.outputs.digest }}
push-to-registry: ${{ steps.build.outputs.wasPushed }}
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by tracing the devcontainers/ci action's handling of the push and refFilterForPush inputs, along with its existing step outputs. Verify the output is true only when the image is pushed successfully and false when the push is filtered out, then exercise it in the YAML workflow scenario described.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- docker, github-actions, typescript
- Ambito
- ci-cd, devops
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 68/100