Skip to main content
bach workflow writes .github/workflows/bach-release.yml into the git repository that holds your bach.toml. The file is a release you start with one button. See One-click releases for what it does.

Behaviour

  • It needs a bach.toml in the folder and a git repository around it, and stops with a sentence saying which is missing.
  • It fills in the install and build steps for Rust, Tauri, Electron and .NET projects, and for the package manager the lock file names (npm, pnpm, Yarn or Bun). For an unrecognised project the Build your app step holds a TODO.
  • The workflow publishes with a write token, so Bach’s action is pinned to the commit of the Bach release you run, found with git ls-remote on github.com/usebach/bach. If that fails (no network, or git is missing), it writes @v0, says so, and pins when you run bach workflow again online. The file explains how to keep the pin current with Dependabot: add package-ecosystem: github-actions to .github/dependabot.yml.
  • A file that starts with # Generated by Bach is updated in place. Any other file with that name is left alone unless you pass --force.
  • If the repository has no GitHub origin, it says so: the workflow appears under Actions once the repository is on GitHub.
  • bach init calls this for you in a GitHub checkout; bach init --no-workflow skips it.