(Doc+) Delineate Bootstrapping Data Stream from Alias#107976
Merged
stefnestor merged 2 commits intomainfrom May 2, 2024
Merged
(Doc+) Delineate Bootstrapping Data Stream from Alias#107976stefnestor merged 2 commits intomainfrom
stefnestor merged 2 commits intomainfrom
Conversation
👋 howdy, team! This is follow-up to [elasticsearch#107327](#107327). I realized my mistake was that we had duplicate sentences in different sections so I edited the wrong area. However, it seemed like a good opportunity to consider clarifying the page better by fixing header links so that the sub-sections reflect as sub-headers instead of all being equal. Thoughts?
Contributor
|
Documentation preview: |
Collaborator
|
@stefnestor please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
Collaborator
|
Pinging @elastic/es-docs (Team:Docs) |
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
shainaraskas
added a commit
to shainaraskas/elasticsearch
that referenced
this pull request
Jun 21, 2024
* (Doc+) Delineate Bootstrapping Data Stream from Alias 👋 howdy, team! This is follow-up to [elasticsearch#107327](elastic#107327). I realized my mistake was that we had duplicate sentences in different sections so I edited the wrong area. However, it seemed like a good opportunity to consider clarifying the page better by fixing header links so that the sub-sections reflect as sub-headers instead of all being equal. Thoughts? * Apply suggestions from code review Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --------- Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> (cherry picked from commit a3f3f59)
This was referenced Jun 21, 2024
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jun 21, 2024
) * (Doc+) Delineate Bootstrapping Data Stream from Alias 👋 howdy, team! This is follow-up to [elasticsearch#107327](#107327). I realized my mistake was that we had duplicate sentences in different sections so I edited the wrong area. However, it seemed like a good opportunity to consider clarifying the page better by fixing header links so that the sub-sections reflect as sub-headers instead of all being equal. Thoughts? * Apply suggestions from code review Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --------- Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> (cherry picked from commit a3f3f59) Co-authored-by: Stef Nestor <26751266+stefnestor@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
👋 howdy, team!
This is follow-up to elasticsearch#107327. I realized my mistake was that we had duplicate sentences in different sections so I edited the wrong area. (Sorry again.)
However, it seemed like a good opportunity to (A) fill in links & (B) consider clarifying the page better by fixing header links so that the sub-sections reflect as sub-headers instead of all being equal. Applied forward earlier feedback.
Thoughts? cc: @dakrone