FORJEX
Skip to documentation
Build checks & CI/CD

Build & ship

Build checks & CI/CD

Check your build locally and automate checks on GitHub.

On this page

Check the build locally

Before pushing through the CLI, Forjex detects the project type and runs a build check. If it fails, the push stops so you can fix the errors first.

Run the relevant check
# Node frontends
npm run build

# Go
go build ./...

# Rust
cargo build --release

For Python projects, the current CLI build check installs requirements. Run pytest separately to check your tests, preferably in an activated virtual environment.

Add GitHub Actions

Enable the CI/CD option during repository setup to generate .github/workflows/ci.yml. The workflow is based on the detected language.

  • Node.js: dependency installation, available tests, and the build script.
  • Python: dependency installation and pytest.
  • Go: build and test steps.
  • Rust: Cargo checks and tests.

The CLI generator can replace an existing workflow at this path. The browser connection flow preserves existing workflows and adds missing selected configuration.

Verify the workflow

After pushing, open your GitHub repository's Actions tab and inspect the run. A generated workflow file is not evidence that the workflow passed.

The CLI-generated workflow targets main. The browser connection flow uses the existing repository's default branch. Review branch filters, environment variables, and test commands for your project.

How CI relates to deployment

GitHub Actions and Vercel can run independently on the same push. The generated setup does not guarantee that Vercel waits for a successful Actions run. Configure deployment protection or a deployment workflow if that ordering is required.