Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

removes zsh completion since it does not work (fixes #426) #439

Merged
merged 1 commit into from
Oct 23, 2019

Conversation

maximilien
Copy link
Contributor

Fixes #426

Proposed Changes

  • removes zsh completion as it the code it generates does not work
  • 🧽 Update or clean up current behaviour

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Oct 10, 2019
@knative-prow-robot knative-prow-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 10, 2019
@maximilien
Copy link
Contributor Author

/ok-to-test

@knative-prow-robot knative-prow-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Oct 10, 2019
@knative-metrics-robot
Copy link

The following is the coverage report on the affected files.
Say /test pull-knative-client-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/kn/commands/completion.go 85.7% 100.0% 14.3

@rhuss
Copy link
Contributor

rhuss commented Oct 11, 2019

Looks good to me, but I wonder why would not remove all completions as I think bash completion is also not very helpful (for the reasons mentioned in #426 (comment)). Now it might be even more confusing and raising the question, why bash-completion and not zsh ?

@navidshaikh
Copy link
Collaborator

This works for zsh #443.

@maximilien
Copy link
Contributor Author

maximilien commented Oct 11, 2019

Looks good to me, but I wonder why would not remove all completions as I think bash completion is also not very helpful (for the reasons mentioned in #426 (comment)). Now it might be even more confusing and raising the question, why bash-completion and not zsh ?

Fair. I don't care for BASH completion either. However, I believe @sixolet added it with her first commit. Care to chime in? Keep or scrap BASH completion too?

@maximilien
Copy link
Contributor Author

@rhuss separating BASH completion removal discussions with issue #456.

So if this LGTY then please merge. Thanks.

@rhuss
Copy link
Contributor

rhuss commented Oct 22, 2019

#443 make zsh completion working again (if we don't use [ in our help messages), but I would be happy to also remove it for now (so merging this PR, but still updating via #443)

@navidshaikh wdyt ?

@navidshaikh
Copy link
Collaborator

navidshaikh commented Oct 23, 2019

@rhuss : Sure lets merge this PR since the feature is not usable now. We can conclude on #443 and add it again.

Copy link
Collaborator

@navidshaikh navidshaikh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2019
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maximilien, navidshaikh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [maximilien,navidshaikh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@navidshaikh
Copy link
Collaborator

/test pull-knative-client-integration-tests

@knative-prow-robot knative-prow-robot merged commit 462973c into knative:master Oct 23, 2019
@maximilien maximilien deleted the issue426 branch December 20, 2019 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

zsh completion gives errors
6 participants