Skip to content

fix: error when --pipeline-name matches no pipeline [closes CCS-34] - #927

Draft
openswe-task-force[bot] wants to merge 1 commit into
masterfrom
open-swe/pipeline-name-not-found
Draft

openswe-task-force[bot] wants to merge 1 commit into
masterfrom
open-swe/pipeline-name-not-found

Conversation

@openswe-task-force

@openswe-task-force openswe-task-force Bot commented Sep 14, 2026

Copy link
Copy Markdown

Description

codefresh get builds --pipeline-name <unknown> silently returned every build: the empty-result check tested the SDK response envelope (_.isEmpty(pipelines)), which is never empty, so requestOptions.pipeline was never set and the filter was dropped. Now the check is on docs, and an unmatched name always throws Cannot find any builds with these pipelines names.

Release Note

codefresh get builds --pipeline-name now fails with a clear error when the pipeline name does not exist, instead of silently returning all builds.

Test Plan

  • codefresh get builds --pipeline-name does/not-exist errors out; a valid name still filters correctly.

Made by Open SWE

Security Report — codefresh/cli

Fixed CVEs: 0

Fixed issues: 0

Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
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