bk pipeline create infers repository defaults and shares local starter setup with bk init

Introduced 2026-10-14 · score 0.94

HOW TO USE IT

When creating a pipeline from a Git checkout, run `bk pipeline create` to infer its repository URL and default name from `origin` (or use the checkout directory name); supply a name or `--repository` to override either default. To initialize only a local pipeline file, run `bk init`; use `--template` for noninteractive starter selection, and use `--dry-run` to resolve inputs without creating remote resources or writing files.

WHY THIS HELPS

Create a pipeline from a Git checkout, or initialize its local pipeline file, while preserving existing files and output preferences.

REQUIREMENTS AND LIMITATIONS

• Version: v3.63.0
• name (positional argument): Explicit pipeline name; overrides the inferred default name.
• --repository <URL>: Explicit repository URL; overrides the URL inferred from Git origin.
• --template <name>: Selects a starter explicitly. Documented values: `go`, `node`, `pipenv`, `ruby`, `empty`.
• --no-input: Runs without interactive input; it does not add prompts or local files unless `--template` is supplied.
• --dry-run: Resolves the same name and URL without writing local files or creating a pipeline or webhook; still performs API reads and requires existing authentication configuration.
• --json: The README shows this flag with `--dry-run`; its specific behavior for `pipeline create` is not documented there.
• Prerequisite: Dry-run requires existing authentication configuration and performs API reads.
• Prerequisite: Generated starters need review, commit, and push before building; agents must have the matching runtime and package manager installed.
• Named invocations, redirected input, and `--no-input` do not add prompts or local files unless `--template` is supplied.
• Dry-run still performs API reads and requires the existing authentication configuration.
• Both commands search the checkout root, including from subdirectories and linked worktrees, and leave existing pipeline files unchanged.
• Generated starters need review, commit, and push before building; suitable agents must have matching runtimes.
• Go runs test/vet; Node requires a real test script and adapts installation to npm, pnpm, Yarn, or Bun lockfiles.
• Pipenv/pytest and Bundler/RSpec recommendations require dependency evidence and lockfiles.

FIRST-PARTY EVIDENCE

• https://github.com/buildkite/cli/releases/tag/v3.63.0
• https://github.com/buildkite/cli/pull/1037
• https://github.com/buildkite/cli/blob/v3.63.0/README.md

Check the installed version and the source before using it. Entry JSON

Report a problem with this card