search

kubernetes / website

Kubernetes website and documentation repo:
https://kubernetes.io
Creative Commons Attribution 4.0 International
4.44k stars 14.28k forks source link

Improvement for k8s.io/docs/reference/kubectl/cheatsheet/ #34678

Closed MyKarpenko closed 1 year ago

MyKarpenko commented 2 years ago

please add vim configuration ASAP The new exam platform really needs it

just this

Create your ~/.vimrc (otherwise indentation will be messed up):

set expandtab

set tabstop=2

set shiftwidth=2

k8s-ci-robot commented 2 years ago

@MyKarpenko: This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
sftim commented 2 years ago

The audience for Kubernetes docs is people who use Kubernetes. All users, and not just folks currently in an exam. I do get that CNCF exams can be frustrating - I've done a few myself - but we expect the exams themselves to provide handy tooling. The exam environment can provide a ~/.vimrc if that's what the exam setters decide is helpful.

(that said, if the exam folks made a request to host an editor configuration file on the Kubernetes docs site, and were persuasive enough, it is possible).

SIG Docs' default position is that we don't add any docs, diagrams, cheat sheet lines, sample manifests etc purely because exam candidates would like them. If a requested change is beneficial to the wider end user community then absolutely, we'll consider adding it.

/priority awaiting-more-evidence /language en

MyKarpenko commented 2 years ago

Thank you, a lot Tim for the reply.

an alias k=kubectl or bash completion are also a more Linux documentation trick and it is documented in kubernetes docs I believe this is the same essential not for just exam sake but for any person setting the working environment up

sftim commented 2 years ago

an alias k=kubectl or bash completion are also a more Linux documentation trick and it is documented in kubernetes docs

kubectl is part of Kubernetes. vim is not part of Kubernetes. We don't document how to set up vim or other text editors. See https://kubernetes.io/docs/contribute/style/content-guide/#what-s-allowed

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/website/issues/34678#issuecomment-1329240636): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.