GitHub Action Quick Start
Get started with the Valist GitHub Action to integrate web3 publishing into your CI/CD pipeline

Create an account & project

To publish with the CLI, you first need to create an account & project at the Web Dashboard.
For more information, visit:
Valist provides an extremely easy to integrate GitHub Action that enables you to publish anything from source code snapshots, arbitrary binaries, Docker images, NPM packages, or anything else that you're building in your existing CI/CD pipeline!
It can be found in the GitHub Marketplace below:
Valist Action - GitHub Marketplace
GitHub
Here's what it looks like to publish a release to Valist using the Valist GitHub Action:
1
name: Valist Publish
2
jobs:
3
publish:
4
runs-on: ubuntu-latest
5
steps:
6
- uses: valist-io/valist-github-[email protected]
7
with:
8
private-key: ${{ secrets.PRIVATE_KEY }}
9
account: acme-co
10
project: example
11
release: 0.0.1
12
path: 'build'
Copied!
Super easy!
  • The private-key field maps to your GitHub Repository secret that contains a key with permission on the Valist Project. We strongly recommend this is a fresh key that only has access to the corresponding Valist Project, and that you don't use an Account-level admin key here.
  • The account field maps to your Valist Account
  • The project field maps to the Valist Project you wish to publish to
  • The release field maps to the version/tag you wish to release
  • The files field is a list of files that you wish to publish in the release. In this case, the ** value will publish all files in the repository, creating a source code snapshot.
For a set of examples, check out this repository below:
valist-github-action-examples/.github/workflows at main Β· valist-io/valist-github-action-examples
GitHub
The Valist Action is built to be modular, and compatible with your existing pipeline. There are many ways to configure it! Next, we'll demonstrate how to automatically publish your GitHub Releases with it!
Export as PDF
Copy link