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

Use standard language for Kubectl command descriptions (Trivial issue, typo?) #56908

Closed
hyakuhei opened this Issue Dec 6, 2017 · 7 comments

Comments

Projects
None yet
6 participants
@hyakuhei

hyakuhei commented Dec 6, 2017

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
When running kubectl --help, most commands are documented as singular "Modify X, Deploy Y" however the plugin command is described in plural "Runs a plugin".

What you expected to happen:
Plugin command description should also be singular.

How to reproduce it (as minimally and precisely as possible):
kubectl --help

Anything else we need to know?:
Obviously this is the most trivial of bugs/typos - I was looking for something I could trivially fix to get used to the Kube pipeline, making changes and contributions. The first stage of that seems to be submitting a GH issue.

Environment:

@hyakuhei

This comment has been minimized.

Show comment
Hide comment
@hyakuhei

hyakuhei Dec 6, 2017

This fits squarely in the area/kubectl but I'm not sure how to annotate it appropriately.

hyakuhei commented Dec 6, 2017

This fits squarely in the area/kubectl but I'm not sure how to annotate it appropriately.

@zjj2wry

This comment has been minimized.

Show comment
Hide comment
@zjj2wry

zjj2wry Dec 7, 2017

Member

/sig cli

Member

zjj2wry commented Dec 7, 2017

/sig cli

@hyakuhei

This comment has been minimized.

Show comment
Hide comment
@hyakuhei

hyakuhei Dec 7, 2017

Thanks @zjj2wry

If it's ok with the community I'd like to work up a tiny PR to fix this...

@hyakuhei #dibs on this issue.

hyakuhei commented Dec 7, 2017

Thanks @zjj2wry

If it's ok with the community I'd like to work up a tiny PR to fix this...

@hyakuhei #dibs on this issue.

@hyakuhei

This comment has been minimized.

Show comment
Hide comment
@hyakuhei

hyakuhei Dec 7, 2017

/area kubectl

hyakuhei commented Dec 7, 2017

/area kubectl

@liggitt liggitt added kind/cleanup and removed kind/bug labels Jan 6, 2018

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Apr 6, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot commented Apr 6, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot May 6, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

fejta-bot commented May 6, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Jun 6, 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot commented Jun 6, 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment