BuildBear Logo Full
Documentation
CI/CD Service

Options

A reference for all of the potential options you can include in your GitHub YAML file.

network: [
  {
    chainId
  }
]
contracts: {
  repo,
  branch
}
deploy-command
buildbear-token

* indicates a required option.

network (array*)

An array of network objects, each with a chainId.

  • chainId (number*): The chain ID of the BuildBear sandbox.
  • blockNumber (number): The block number from which to fork the underlying network.

deploy-command (string*)

The deployment command to be run by the CI/CD system to deploy your contracts.

buildbear-token (string*)

The BuildBear API token. If needed, follow these instructions to get an API token.

Managing API Keys

API keys let you use BuildBear programmatically, in a CLI, and connect your GitHub repository to BuildBear's CI/CD service.

Supported Cheatcodes

A reference for all of the supported Foundry cheatcodes you can use in your automated Foundry test.