Skip to content

Add simple defaults to pipeline creation - #1037

Merged
mcncl merged 2 commits into
mainfrom
feat/pipeline_onboarding
Oct 14, 2026
Merged

mcncl merged 2 commits into
mainfrom
feat/pipeline_onboarding

Conversation

@mcncl

@mcncl mcncl commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Description

Creating a pipeline from a repository should not require retyping details the CLI already knows or guessing how to provide its pipeline file.

Changes

  • Infer the repository URL and default name from Git origin, falling back to the checkout directory name. Explicit arguments win.
  • Share local setup with bk init: find existing pipeline files at the repository root, including from subdirectories/worktrees, and never overwrite them. When needed, offer a project-aware recommendation, reviewed Buildkite example templates, or an empty starter, with runtime prerequisites.
  • Give bare interactive creation a concise completion message. File status and starter prompts stay on stderr; explicit formats, configured preferences, and named/scripted output retain their contracts. Dry-run resolves the same inputs without writing files or creating remote resources.

For a repository with an existing pipeline file:

$ bk pipeline create
Pipeline file found at .buildkite/pipeline.yml; leaving it unchanged.
Pipeline created: https://buildkite.com/org/pipeline

Generated starters still need review, commit and push before building, and suitable agents with the required runtimes. This does not change authentication defaults or add preflight, agent readiness checks, or first-build execution.

Testing

  • Tests run locally with env -u BUILDKITE_API_TOKEN mise run test
  • Code formatted with mise run format
  • Lint and build passed; 20 built-CLI TTY/pipe cases passed against a local mock API. No real remote pipelines were created.

mcncl added 2 commits October 14, 2026 04:58
Infer pipeline names and repository URLs from Git origin, and share
repository-root starter setup with bk init. Offer reviewed project-aware
templates without overwriting existing pipeline files.

Keep explicit and noninteractive creation prompt-free, and resolve dry-run
inputs without generating local files or creating remote resources.

Amp-Thread-ID: T-31916b17-e269-4fb9-8102-3718bc47aaa5
Default guided creation to a concise completion line while preserving
explicit format flags, configured preferences and scripted output.
Keep repository-relative file status and starter prompts on stderr so
structured stdout stays parseable.

Amp-Thread-ID: https://ampcode.com/threads/T-31916b17-e269-4fb9-8102-3718bc47aaa5
@mcncl
mcncl requested review from a team as code owners October 14, 2026 05:19
@mcncl
mcncl merged commit 3c07ef8 into main Oct 14, 2026
2 checks passed
@mcncl
mcncl deleted the feat/pipeline_onboarding branch October 14, 2026 05:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant