-
Notifications
You must be signed in to change notification settings - Fork 112
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
Fix TOC for chef-vault #3176
Fix TOC for chef-vault #3176
Conversation
👷 Deploy Preview for chef-workstation processing.
|
@chuhn can you add your DCO signoff to your commit. |
OK, how do I do that technically? Edit the commit and force-push the MR branch? |
Yeah |
The levels of the headings in this document are pretty messed up. It has 3 major sections: 1. knive vault 2. Using chef-vault in cookbooks 3. Using chef-vault standalone Also "Example Commands" should be one level above the specific commands, not in the same level. Signed-off-by: Christopher Huhn <C.Huhn@gsi.de>
OK, DCO done. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
The levels of the headings in this document are pretty messed up. It has 3 major sections:
Also "Example Commands" should be one level above the specific commands, not in the same level.
Related Issue
I think the documentation of
knife vault
should be split out into a separate document and references from here.Types of changes
Checklist:
Gemfile.lock
has changed, I have used--conservative
to do it and included the full output in the Description above.