Skip to content

Conversation

lhirlimann
Copy link
Member

Explain what to do to ingest the root of the share point server.

This is a doc change

Explain what to do to ingest the root of the share point server.
@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label v9.2.0 external-contributor Pull request authored by a developer outside the Elasticsearch team labels Sep 2, 2025
@elasticsearchmachine
Copy link
Collaborator

@lhirlimann please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

@lhirlimann lhirlimann added >docs General docs changes and removed needs:triage Requires assignment of a team area label external-contributor Pull request authored by a developer outside the Elasticsearch team v9.2.0 labels Sep 2, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Docs Meta label for docs team label Sep 2, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/core-docs (Team:Docs)

@github-actions
Copy link
Contributor

github-actions bot commented Sep 2, 2025

🔍 Preview links for changed docs

@github-actions
Copy link
Contributor

github-actions bot commented Sep 2, 2025

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

@lhirlimann
Copy link
Member Author

@lhirlimann please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

I'm unable to find this :(

@eedugon eedugon added the v9.2.0 label Sep 3, 2025
Copy link
Contributor

@eedugon eedugon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I have suggested a new change based on @leemthompo's comment.

If you believe the change makes sense and looks better please apply it and we would be ready to merge!

@leemthompo leemthompo requested a review from a team September 4, 2025 07:31
Copy link
Member

@jedrazb jedrazb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@leemthompo leemthompo added auto-backport Automatically create backport pull requests when merged v9.0.0 v9.1.0 labels Sep 4, 2025
@leemthompo
Copy link
Contributor

Thanks @lhirlimann!

@leemthompo leemthompo merged commit d5fa4e6 into main Sep 4, 2025
11 checks passed
@leemthompo leemthompo deleted the lhirlimann-patch-3 branch September 4, 2025 08:30
phananh1010 added a commit to phananh1010/elasticsearch that referenced this pull request Sep 4, 2025
phananh1010 added a commit to phananh1010/elasticsearch that referenced this pull request Sep 4, 2025
phananh1010 added a commit to phananh1010/elasticsearch that referenced this pull request Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged >docs General docs changes Team:Docs Meta label for docs team v9.0.0 v9.1.0 v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants