Contract CI/CD

Stagenets provide a Continuous Integration and Delivery (CI/CD) pipeline for smart contracts. They:

Connect to GitHub repositories containing Hardhat or Foundry projects
Import and compile their smart contracts
Automatically create a dedicated Contract Workspace for each one

After connection, when a new contract is pushed to the repository, it is picked up automatically and has a new Workspace created for it.

When changes to existing contracts are pushed, they are also picked up automatically, and the updated contract is recorded as a new Contract Version within its Workspace.

When Contract Versions are deployed to the Stagenet, they are automatically recorded as Contract Deployments within their Workspace.

Contract versioning diagram showing a workspace with multiple versions and deployments

Each Workspace provides a single, scoped place to analyse and manage a contract as you develop. In practice, the flow looks like this:

Link a GitHub repository to a Stagenet and create a Workspace for each of its contracts.
Deploy the repository’s contracts to the Stagenet and analyse them in their Workspace’s Views.
Push contract updates to GitHub to update their Workspace with new Contract Versions.
Navigate Contract Versions and Deployments via the Workspace’s History View.

Set Up CI/CD

Follow your framework’s quickstart to connect a GitHub repository to a Stagenet and setup CI/CD:

Foundry QuickstartHardhat V2 QuickstartHardhat V3 Quickstart