-
Notifications
You must be signed in to change notification settings - Fork 97
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
Formally turn snippet into module #3661
Formally turn snippet into module #3661
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We generally use level 1 headings and then use leveloffsets when including modules. However, this is a very special use case: limited to "master.adoc" files, upstream only, and always immediately after the intial heading if at all.
LGTM.
You are right, Max, let's try to do things properly. The module now has a level 1 heading and a leveloffset is applied for the include directives. Can you please re-review @maximiliankolb? |
(cherry picked from commit b46d0d3) Applies the change to one more guide (Administering with Ansible)
Merged to "master" but no cherry-picks because 3.13 has one more guide that is also affected by this. To be extra safe, I want to do a separate PR: #3669 |
What changes are you introducing?
Turning the 'guide not ready yet' snippet into a proper module with its own heading.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
This came up in #3653. Adding the ribbon/banner causes build failures if there are headings missing in certain places. The 'guide not ready yet' snippet is one of them.
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
N/A
Checklists
Please cherry-pick my commits into: