---
next_cursor: eyJzY29yZSI6MCwic2VxIjoxNzg0LCJzaW5jZSI6bnVsbCwidG9vbCI6ImJrIiwidiI6MX0
has_more: true
next: https://sincecutoff.com/v1/changes.md?tool=bk&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxNzg0LCJzaW5jZSI6bnVsbCwidG9vbCI6ImJrIiwidiI6MX0
items: 10
---
# sincecutoff.com changes: bk

## bk organizations list adds an org alias and JSON output (bk, 2026-01-05)
Published 2026-10-19
- slug: bk-organizations-list-adds-an-org-alias-and-json-output-281f55760887
- score: 0.92

How to use it:

When you need to list organizations configured for Buildkite CLI, run `bk org list`; JSON is the default, and each organization has a `selected` value indicating whether it is active.

Examples:

```
bk org list
```

- why_it_matters: List the organizations available to the current Buildkite CLI configuration.
- sources: <https://github.com/buildkite/cli/releases/tag/v3.17.0>, <https://github.com/buildkite/cli/pull/597>, <https://github.com/buildkite/cli/blob/v3.17.0/cmd/organization/list.go>, <https://github.com/buildkite/cli/blob/v3.17.0/main.go>, <https://buildkite.com/docs/platform/cli/configuration>
- gotchas: "Version: v3.17.0"; "org: Alias for the `organization` command group."; "-o, --output: Select `json`, `yaml`, or `text` output format; JSON is the default."; "selected: Boolean indicating whether the organization is selected in the current CLI configuration."; "Prerequisite: Install and configure the Buildkite CLI with an API access token and an organization. The command lists configured organizations."; "Docs conflict: Current CLI reference documents `bk organization list`; the v3.17.0 source confirms `org` as an alias. Current configuration docs describe `bk auth switch` as replacing deprecated `bk use`, while the v3.17.0 release note names `use`."

## bk pipeline copy adds cp and cross-organization copying (bk, 2026-01-05)
Published 2026-10-19
- slug: bk-pipeline-copy-adds-cp-and-cross-organization-copying-9195a81df64e
- score: 0.98

How to use it:

When copying a pipeline within or across organizations, use `bk pipeline cp`; omit the source to select it interactively or pass its slug or `org/slug`. Set `--target` to the new pipeline name or `org/name`; for a cross-organization copy into an organization using clusters, provide `--cluster` with the target cluster ID.

Examples:

```
bk pipeline cp <source-pipeline> --target <new-pipeline>
```

```
bk pipeline cp <source-org>/<source-pipeline> --target <target-org>/<new-pipeline> --cluster <target-cluster-id>
```

```
bk pipeline cp <source-pipeline> --target <new-pipeline> --dry-run
```

- why_it_matters: Copy a pipeline within an organization or across configured organizations.
- sources: <https://github.com/buildkite/cli/releases/tag/v3.17.0>, <https://github.com/buildkite/cli/pull/600>, <https://raw.githubusercontent.com/buildkite/cli/v3.17.0/cmd/pipeline/copy.go>, <https://buildkite.com/docs/platform/cli/configuration>
- gotchas: "Version: v3.17.0"; "<pipeline>: Source pipeline slug or org/slug; omitted source is resolved from current context or prompted for."; "--target, -t <target>: New pipeline name or org/name. If omitted, prompts for a target."; "--cluster, -c <cluster>: Target cluster name or ID; required for cross-organization copies if the target organization uses clusters."; "--dry-run: Show what would be copied without creating the pipeline."; "--output, -o <format>: Output format: json, yaml, or text."; "Prerequisite: Configure the CLI with an API access token and organization. Configure an individual token for each organization you need to use."; "Prerequisite: The v3.17.0 command prompts for a target cluster ID on a cross-organization copy if `--cluster` is omitted; the cluster may be required when the target organization uses clusters."; "Cross-organization copying applies when the organizations are configured."; "Docs conflict: Current CLI reference documents `--cluster-name` and `--cluster-uuid`; v3.17.0 source documents `--cluster` instead. Use the versioned v3.17.0 flag for this card: https://buildkite.com/docs/platform/cli/reference/pipeline"

## bk adds the job log command (bk, 2026-01-15)
Published 2026-10-19
- slug: bk-adds-the-job-log-command-6cb145be4e5c
- score: 0.97

How to use it:

When debugging or reviewing a Buildkite CI job, run `bk job log <job-id>` to view its logs. Replace `<job-id>` with the job UUID.

Examples:

```
bk job log <job-id>
```

- why_it_matters: View logs for a Buildkite job while debugging or reviewing a repository’s CI run.
- sources: <https://github.com/buildkite/cli/releases/tag/v3.20.0>, <https://buildkite.com/docs/platform/cli/reference/job>, <https://buildkite.com/docs/platform/cli>, <https://buildkite.com/docs/apis/rest-api/jobs>
- gotchas: "Version: v3.20.0"; "<job-id> (required): Job UUID to get logs for."; "Prerequisite: Install and configure the Buildkite CLI with an API access token for the organization."; "Prerequisite: The token needs the `read_build_logs` scope to retrieve job logs."

## bk adds a config command for set/get (bk, 2026-01-18)
Published 2026-10-19
- slug: bk-adds-a-config-command-for-set-get-a14fd32736d3
- score: 0.96

How to use it:

When setting or retrieving `bk` configuration, use `bk config set <key> <value>` or `bk config get <key>`. Configuration keys include `output_format`, `selected_org`, `no_pager`, `quiet`, `no_input`, and `pager`.

Examples:

```
bk config get <key>
```

```
bk config set <key> <value> [--local]
```

- why_it_matters: Set or retrieve configuration using the `bk` CLI.
- sources: <https://github.com/buildkite/cli/releases/tag/v3.22.0>, <https://github.com/buildkite/cli/pull/623/files>
- gotchas: "Version: v3.22.0"; "<key> (required): One of `selected_org`, `output_format`, `no_pager`, `quiet`, `no_input`, or `pager`."; "<value> (required): Value for the key. `output_format` accepts `json`, `yaml`, or `text`; `no_pager`, `quiet`, and `no_input` accept `true` or `false`."; "--local: Set the value in local repo configuration. `no_input` and `pager` are user-config-only keys."

## bk auth adds OAuth login and logout (bk, 2026-02-11)
Published 2026-10-19
- slug: bk-auth-adds-oauth-login-and-logout-373a4d85488f
- score: 0.92

How to use it:

When working in a Buildkite repository, authenticate with `bk auth login --org <organization-slug>` to open the browser OAuth flow and store the token in the system keychain. Use `bk auth logout [<organization-slug>]` to clear credentials for an organization; the v3.24.0 command also clears its config token.

Examples:

```
bk auth login --org <organization-slug>
```

```
bk auth login --org <organization-slug> --scopes "<scope> <scope>"
```

```
bk auth logout [<organization-slug>]
```

- why_it_matters: Authenticate the bk CLI with OAuth when working in a repository that uses Buildkite.
- before: The release note says the temporary `auth` alias for `configure` was removed; it does not document the earlier command invocation.
- sources: <https://github.com/buildkite/cli/releases/tag/v3.24.0>, <https://github.com/buildkite/cli/pull/637>, <https://github.com/buildkite/cli/blob/v3.24.0/cmd/auth/login.go>, <https://github.com/buildkite/cli/blob/v3.24.0/cmd/auth/logout.go>, <https://buildkite.com/docs/platform/cli/installation>
- gotchas: "Version: v3.24.0"; "login --org <organization-slug> (required): Organization slug for OAuth login."; "login --scopes <scopes>: OAuth scopes to request; examples include `read_user read_organizations read_clusters write_clusters`."; "logout [<organization-slug>]: Organization slug; defaults to the currently selected organization. If neither is available, the command errors."; "Prerequisite: Install the Buildkite CLI; v3.24.0 is the version covered by the cited command source."; "Prerequisite: OAuth login opens a browser and stores the resulting token in the system keychain when available; it also writes the token to config for fallback/compatibility."; "OAuth support is initial."; "OAuth client ID is injected into built binaries."; "Tokens remain in text-based config; removing them is still to come."; "Docs conflict: Current auth documentation reflects newer CLI behavior: it lists login flags such as `--device` and `--token`, whereas v3.24.0 source requires `--org` and documents `--scopes`. Use the v3.24.0 source for this card."

## bk job adds reprioritize and priority commands (bk, 2026-02-11)
Published 2026-10-19
- slug: bk-job-adds-reprioritize-and-priority-commands-af62e4f7c23a
- score: 0.96

How to use it:

When the target job is in a running Buildkite build, set its new priority with `bk job reprioritize` and the job UUID and integer priority. The `bk job priority` alias is stated in the v3.24.0 release note; the official CLI reference documents `reprioritize`.

Examples:

```
bk job reprioritize <job-uuid> <priority>
```

- why_it_matters: Change the priority of a job in a running Buildkite build.
- sources: <https://github.com/buildkite/cli/releases/tag/v3.24.0>, <https://github.com/buildkite/cli/pull/641>, <https://buildkite.com/docs/platform/cli/reference/job>, <https://buildkite.com/docs/apis/rest-api/jobs>, <https://buildkite.com/docs/platform/cli/configuration>
- gotchas: "Version: v3.24.0"; "<job-id> (required): UUID of the job to reprioritize."; "<priority> (required): New priority value for the job. API docs specify an integer; higher values indicate higher priority."; "-p, --pipeline: Pipeline slug or `org/pipeline`; current CLI reference marks this flag deprecated and ignored."; "-b, --build-number: Build number; current CLI reference marks this flag deprecated and ignored."; "Prerequisite: Configure the Buildkite CLI with an API access token."; "Prerequisite: The REST API reprioritize operation requires the `write_builds` scope."; "The job must be in a running build."; "Docs conflict: The v3.24.0 source example shows `-b <build>` and says `--pipeline` and `--build` are required unless the pipeline is configured for the current Git repository; the current CLI reference says both flags are deprecated and ignored. Follow the v3.24.0 source for that version-specific invocation if needed: https://github.com/buildkite/cli/blob/v3.24.0/cmd/job/reprioritize.go"; "Docs conflict: The v3.24.0 release note names `job priority` as an alias, but the official CLI reference documents only `bk job reprioritize`; alias syntax was not found."

## bk secret adds secret management commands (bk, 2026-02-11)
Published 2026-10-19
- slug: bk-secret-adds-secret-management-commands-28e66abe6055
- score: 0.96

How to use it:

When managing Buildkite secrets, use `bk secret` with the cluster ID and the relevant `create`, `update`, `delete`, `list`, or `get` subcommand. For example, create with `--cluster-id`, `--key`, and `--value`; the value can be entered interactively when omitted.

Examples:

```
bk secret create --cluster-id <cluster-id> --key <key> --value "<secret-value>"
```

```
bk secret update --cluster-id <cluster-id> --secret-id <secret-id> --description "<description>"
```

```
bk secret list --cluster-id <cluster-id>
```

- why_it_matters: Manage secrets while maintaining a Buildkite pipeline.
- sources: <https://github.com/buildkite/cli/releases/tag/v3.24.0>, <https://github.com/buildkite/cli/pull/638>, <https://github.com/buildkite/cli/blob/v3.24.0/cmd/secret/create.go>, <https://github.com/buildkite/cli/tree/v3.24.0/cmd/secret>, <https://buildkite.com/docs/platform/cli/reference/secret>
- gotchas: "Version: v3.24.0"; "--cluster-id <cluster-id> (required): Cluster ID; the v3.24.0 create command requires it."; "--key <key> (required): Secret key name, such as MY_SECRET."; "--value <value>: Secret value. If omitted, the CLI prompts interactively; with `--no-input`, it is required."; "--description <description>: Description of the secret; on update, changes the description."; "--policy <policy>: Secret access policy in YAML format."; "--secret-id <secret-id> (required): Secret ID used by get, update, and delete."; "--update-value: Prompt to update the secret value."; "--output, -o <format>: Output format: json, yaml, or text."; "--cluster-uuid <uuid>: Current online reference uses this cluster selector; it differs from the v3.24.0 source's `--cluster-id`."; "Docs conflict: The current Buildkite CLI reference uses `--cluster-uuid`; v3.24.0 source uses `--cluster-id`. Use `--cluster-id` for the card's stated version."

## bk pipeline convert supports GitLab, Bitrise, and Harness (bk, 2026-02-18)
Published 2026-10-19
- slug: bk-pipeline-convert-supports-gitlab-bitrise-and-harness-06536d89e031
- score: 0.97

How to use it:

When converting a GitLab CI, Bitrise, or Harness CI file, run `bk pipeline convert` with the file path and specify `--vendor` if it cannot be detected from the filename. These conversions are beta; output defaults to `.buildkite/pipeline.<vendor>.yml`, or use `--output` to choose a path.

Examples:

```
bk pipeline convert -F <pipeline-file> --vendor <gitlab|bitrise|harness>
```

```
bk pipeline convert -F <pipeline-file> --vendor <gitlab|bitrise|harness> -o <output-file>
```

- why_it_matters: Convert a GitLab CI, Bitrise, or Harness CI pipeline configuration to Buildkite format.
- before: Use the existing supported vendor conversions; GitLab, Bitrise, and Harness are not listed among them.
- sources: <https://github.com/buildkite/cli/releases/tag/v3.25.0>, <https://github.com/buildkite/cli/pull/646>, <https://buildkite.com/docs/platform/cli/reference/pipeline>, <https://buildkite.com/docs/pipelines/converter>
- gotchas: "Version: v3.25.0"; "Availability: GitLab, Harness, and Bitrise are beta."; "-F, --file (required): Path to the pipeline file to convert."; "-v, --vendor: CI/CD vendor; auto-detected if the file name matches a vendor path and name, otherwise specify it. Supported values include gitlab, bitrise, and harness."; "-o, --output: Custom path to save the converted pipeline; default is `.buildkite/pipeline.<vendor>.yml`."; "Prerequisite: Install the Buildkite CLI. Official docs show `brew install buildkite/buildkite/bk`."; "Prerequisite: No API token is required; conversion uses a public conversion API."; "The command converts supported CI/CD pipeline configurations to Buildkite format."; "Vendor is automatically detected from the filename when not specified."; "By default, output is saved to `.buildkite/pipeline.<vendor>.yml`."; "No API token is required because the command uses a public conversion API."; "Docs conflict: The current CLI reference and converter overview do not list Harness as a supported CLI vendor, while the v3.25.0 release note does. Used the release note for v3.25.0 vendor availability; current docs may describe a later state."

## bk pipeline create can opt in to webhook creation (bk, 2026-02-18)
Published 2026-10-19
- slug: bk-pipeline-create-can-opt-in-to-webhook-creation-b886c546d24c
- score: 0.98

How to use it:

When creating a Buildkite pipeline for a GitHub or GitHub Enterprise repository, add `--create-webhook` (or `-W`) to opt in to creating its SCM webhook.

Examples:

```
bk pipeline create "<pipeline-name>" --description "<description>" --repository "<github-repository-url>" --create-webhook
```

- why_it_matters: Create a Buildkite pipeline from the CLI and have it create webhooks for the pipeline's GitHub repository.
- sources: <https://github.com/buildkite/cli/releases/tag/v3.25.0>, <https://github.com/buildkite/cli/pull/647>, <https://buildkite.com/docs/platform/cli/reference/pipeline>, <https://buildkite.com/docs/platform/cli>
- gotchas: "Version: v3.25.0"; "<name> (required): Pipeline name."; "--repository, -r: Repository URL; provide the GitHub repository URL for this task."; "--description, -d: Pipeline description."; "--create-webhook, -W: Create an SCM webhook for the pipeline; documented for GitHub and GitHub Enterprise only. Opt-in flag."; "Prerequisite: Install the Buildkite CLI and authenticate it with an API access token to use Buildkite organizations."; "Prerequisite: The webhook flag supports GitHub and GitHub Enterprise only."; "Webhook creation is opt-in."

## bk pipeline convert accepts piped stdin (bk, 2026-02-20)
Published 2026-10-19
- slug: bk-pipeline-convert-accepts-piped-stdin-1736ed4f4d24
- score: 0.99

How to use it:

When converting a GitHub Actions pipeline from standard input, run `bk pipeline convert` with `--vendor github` and omit `--file`. Output goes to stdout by default; use `--output`/`-o` to save it to a file.

Examples:

```
cat ci.yml | bk pipeline convert --vendor github
```

```
cat ci.yml | bk pipeline convert --vendor github -o <output-path>
```

- why_it_matters: Convert a GitHub pipeline configuration supplied through standard input.
- sources: <https://github.com/buildkite/cli/releases/tag/v3.26.0>, <https://github.com/buildkite/cli/pull/656>, <https://buildkite.com/docs/pipelines/converter>
- gotchas: "Version: v3.26.0"; "--vendor (required): Specifies the source CI/CD vendor; use `github` for GitHub Actions."; "--file: Path to the pipeline file. Omit when piping configuration from stdin."; "--output / -o: Path to save the converted pipeline; when omitted for stdin input, output is printed to stdout."; "Prerequisite: Install the Buildkite CLI; the docs show `brew install buildkite/buildkite/bk`."

Next: https://sincecutoff.com/v1/changes.md?tool=bk&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxNzg0LCJzaW5jZSI6bnVsbCwidG9vbCI6ImJrIiwidiI6MX0
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->