Skip to content

fix: address completion follow-up issues (#35-#39, #41)#46

Merged
rbansal42 merged 3 commits intodevfrom
feature/completion-followup
Feb 13, 2026
Merged

fix: address completion follow-up issues (#35-#39, #41)#46
rbansal42 merged 3 commits intodevfrom
feature/completion-followup

Conversation

@rbansal42
Copy link
Owner

Summary

Addresses all follow-up issues from the v0.3.0 dynamic shell completions release:

Code Review Fixes

  • Aligned pipeline --status completion values with API state model (IN_PROGRESS/SUCCESSFUL instead of BUILDING/ERROR)
  • Removed misleading --branch completion from repo clone (resolves from CWD, not target repo)
  • Added clarifying comment on root --repo persistent flag shadowing behavior

Follow-up Issues Created

Testing

  • go build ./... — passes
  • go test ./... — all tests pass
  • go vet ./... — clean

rbansal42 and others added 3 commits February 13, 2026 18:54
Merge dev: dynamic shell completions
- Add doc comment explaining filterPrefix redundancy with Cobra (#35)
- Extract magic numbers into named constants (completionPageLimit, completionPRPageLimit) (#36)
- Add Username to member completion fallback chain (#37)
- Add --branch flag completion to browse command (#38)
- Document 'on hold' space issue in issue list completion (#39)
- Add completions for repo clone/delete/view/fork/sync/setdefault (#41)
- Add --status and --branch completions to pipeline list (#41)
- Add --role completion to snippet list (#41)
- Register global --repo persistent flag completion on root command (#41)
- Align pipeline list --status completion values with API state model
  (use IN_PROGRESS/SUCCESSFUL instead of BUILDING/ERROR)
- Remove misleading --branch completion from repo clone
  (CompleteBranchNames resolves from CWD, not the target repo)
- Add clarifying comment on root --repo persistent flag shadowing
@rbansal42 rbansal42 merged commit a510c72 into dev Feb 13, 2026
2 checks passed
@rbansal42 rbansal42 deleted the feature/completion-followup branch February 13, 2026 13:36
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.

2 participants