This action allows you to push a block to Contensis CMS in your own Github Actions
Required The id of the block to push to
Required 'The Contensis cloud alias to connect to'
The id of the project to connect to. Default: "website"
Required Client id to connect to the supplied alias
Required Shared secret to use with the supplied client id
The uri of the container image to build the block from. Default: "ghcr.io/${{ github.repository }}/${{ github.ref_name }}/app:latest" e.g. "ghcr.io/contensis/leif/master/app:latest"
The branch name in Contensis to push the block to. Default: ${{ github.ref_name }}
Whether to release the block upon successful push. Default: false
Whether to make the block live upon successful push. Default: false
Whether to push a tag to the git repo upon successful block push. Default: false
The git token from secrets to use when pushing to the git repo upon successful block push. Default: ${{ github.token }}
The version number of the pushed block
The pushed tag name if tag-repo input is true
uses: contensis/block-push@v1
with:
block-id: name-of-block
alias: example-dev
project-id: website
client-id: ${{ secrets.CONTENSIS_CLIENT_ID }}
shared-secret: ${{ secrets.CONTENSIS_SHARED_SECRET }}Push a block called name-of-block, set it to release automatically, and push a git tag containing the block version number
- name: Push block to Contensis
id: push-block
uses: contensis/block-push@v1
with:
block-id: name-of-block
release: true
alias: example-dev
project-id: website
client-id: ${{ secrets.CONTENSIS_CLIENT_ID }}
shared-secret: ${{ secrets.CONTENSIS_SHARED_SECRET }}
tag-repo: true
git-token: ${{ github.token }}- Include
id: push-blockattribute to reference the job step later (e.g. to access outputs insteps.push-block.outputs.*)
- name: Echo push-block outputs
run: |
echo block-version: ${{ steps.push-block.outputs.block-version }}
echo git-tag: ${{ steps.push-block.outputs.git-tag }}