Skip to main content
This page gets your machine ready to contribute to any of the three repos. Total time is about twenty minutes the first time, and everything here is free.

​
Accounts

1

Create or sign in to GitHub

All contribution happens through GitHub. Sign in at github.com, then fork the repo you want to change. You never push directly to the main repos; you push to your fork and open a pull request.
2

Get a Biznet GIO API token

The providers talk to Biznet GIO with an API token, created from the portal as described in Authentication. You only need this to run plan, apply, preview, or up. Static checks like terraform validate and pulumi preview with mocks work without it.
3

Optionally create a Pulumi Cloud account

Running the Pulumi examples with real state requires a free Pulumi Cloud account, and the CI pipeline needs a personal access token from it. Skip this until you actually run something.

​
Tooling

Install exactly the versions this project uses. The CI pipelines pin the same ones, so a change that builds on your machine builds in CI: Go 1.25 is not a typo. The Pulumi Go SDK’s go.mod declares a recent toolchain requirement, so older Go versions refuse to build. If you see a go: go.mod requires go >= 1.25 error, update Go.
You do not need all six Pulumi language toolchains. Install the one you want to contribute in. The CI pipeline runs all six for you anyway.

​
Cloning and first run

The three repos are plain git clones:
These commands clone the upstream repos directly. If you plan to send a pull request, fork first and clone your fork instead, the same way. Then verify each one works on your machine.

​
Docs site

Every saved change hot-reloads. The local preview is the best way to check MDX before committing.

​
Terraform examples

All three commands must pass. They need no credentials; terraform validate is a static check that never calls the Biznet GIO API.

​
Pulumi examples

One build command per language, from inside the example folder:
YAML needs no build; any YAML parser accepting yaml/neolite/Pulumi.yaml is the check.

​
CI secrets, for maintainers

The example repos’ pipelines run on manual dispatch and most actions need repo secrets. Configure these in your fork’s Settings > Secrets and variables > Actions if you want to run the full pipelines from your own fork: Never set these unless you mean it. apply, up, and destroy place real orders on the account whose token you configure, which is exactly why the pipelines are manual only. See Pipelines for the full explanation.

​
You are ready

From here, read Conventions so your first change matches the house style, then pick a walkthrough from the step-by-step guide.