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

explain how we submit PRs for generated command docs in CONTRIBUTING.md #893

Closed
neolit123 opened this issue Jun 6, 2018 · 1 comment
Closed
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone

Comments

@neolit123
Copy link
Member

the submission for k/website PRs about things like kubeadm commands has to be explained in detail, so that we can get other folks working on documenting new commands.

right now i believe only me and @fabriziopandini know how to do that from the kubeadm team.

the addition should be made in the CONTRIBUTING.md file in the k/kubeadm repo.

@timothysc @Bradamant3

@neolit123 neolit123 added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/documentation Categorizes issue or PR as related to documentation. labels Jun 6, 2018
@neolit123 neolit123 self-assigned this Jun 6, 2018
@neolit123
Copy link
Member Author

idea came from from the discussion here:
#842

@timothysc timothysc added this to the v1.12 milestone Jul 3, 2018
@neolit123 neolit123 added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Aug 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

2 participants