docker/babashka-pod-docker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Only release on tags

Browse Source
This commit is contained in:
James Carnegie
2023-02-06 23:23:24 +00:00
parent a8ef14e5a0
commit 26cda189da
2 changed files with 13 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.github/workflows/release.yml vendored
View File

@@ -2,8 +2,8 @@ name: Release
on: on:
push: push:
branches: tags:
- main - 'v[0-9]+.[0-9]+.[0-9]+'
jobs: jobs:
releases-matrix: releases-matrix:
@@ -26,6 +26,6 @@ jobs:
goarch: ${{ matrix.goarch }} goarch: ${{ matrix.goarch }}
goversion: 1.19.1 goversion: 1.19.1
binary_name: "pod-atomisthq-tools.docker" binary_name: "pod-atomisthq-tools.docker"
release_tag: v0.${{ github.run_number }}.${{ github.run_attempt }} release_tag: ${{github.ref_name}}
overwrite: TRUE overwrite: TRUE
compress_assets: OFF compress_assets: OFF

4
README.md
View File

@@ -47,6 +47,10 @@ Create `vonwig/pod-atomisthq-tools.docker` which is a manifest list with pod bin
bb build-pod-image bb build-pod-image
``` ```
## Releasing
Pushing a tag (like v0.1.1) will cause a GitHub release to be created
## Namespace generation ## Namespace generation
The `pods/load-pod` call is convenient for a repl-session, or a script, but what if you are `aot` compiling, or building a native binary. In the example above, the namespaces emitted by `pods/load-pod` are not available until runtime. The `pods/load-pod` call is convenient for a repl-session, or a script, but what if you are `aot` compiling, or building a native binary. In the example above, the namespaces emitted by `pods/load-pod` are not available until runtime.