[DOCS] Explicitly set section IDs for Asciidoctor migration #41550
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Pinging @elastic/es-docs |
jrodewig
added a commit
that referenced
this pull request
Apr 25, 2019
jrodewig
added a commit
that referenced
this pull request
Apr 25, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following page URLs contain autogenerated IDs:
_literal_collectors_literal_section)_literal_query_literal_section)_literal_rewrite_literal_section)With the Asciidoctor migration, these IDs would change and result in broken links.
This explicitly sets the IDs so the page URLs are stable during Asciidoctor migration.
I plan to backport this to 2.2. Relates to #41128 and elastic/docs#827.