[Docs] Restore troubleshooting content #2628
Merged
Conversation
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
picandocodigo
approved these changes
Apr 10, 2025
This was referenced Apr 10, 2025
marciw
added a commit
to elastic/docs-content
that referenced
this pull request
Apr 11, 2025
Troubleshooting content for the clients has moved back to the client docs repos. This PR makes corresponding changes in docs-content. Related PRs: elastic/elasticsearch-java#988 elastic/elasticsearch-js#2727 elastic/elasticsearch-net#8490 elastic/elasticsearch-ruby#2628 elastic/elasticsearch-js#2729
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.
👀 Preview
(the release notes section at the bottom of the left nav won't be there in the full build)
This PR restores the troubleshooting topics that were migrated to docs-content.
I'll open a separate PR to remove these from the docs-content repo once this is merged.