Skip to content
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

[DOCS] Fix typo for the Reset Features API #111731

Merged
merged 1 commit into from
Aug 13, 2024
Merged

Conversation

renshuki
Copy link
Contributor

@renshuki renshuki commented Aug 9, 2024

Fix minor typo in the doc for the Reset Features API

@renshuki renshuki added the Team:Docs Meta label for docs team label Aug 9, 2024
Copy link
Contributor

github-actions bot commented Aug 9, 2024

Documentation preview:

@elasticsearchmachine elasticsearchmachine added v8.15.1 needs:triage Requires assignment of a team area label external-contributor Pull request authored by a developer outside the Elasticsearch team labels Aug 9, 2024
@elasticsearchmachine
Copy link
Collaborator

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

@elasticsearchmachine elasticsearchmachine removed the Team:Docs Meta label for docs team label Aug 9, 2024
@renshuki renshuki added >docs General docs changes Team:Docs Meta label for docs team labels Aug 9, 2024
@elasticsearchmachine
Copy link
Collaborator

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

@elasticsearchmachine elasticsearchmachine removed the needs:triage Requires assignment of a team area label label Aug 9, 2024
Copy link
Contributor

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

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

thank you!

@renshuki renshuki merged commit eedf52c into 8.15 Aug 13, 2024
7 checks passed
@renshuki renshuki deleted the fix-typo-reset-features-api branch August 13, 2024 00:27
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
7.17

@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

The backport operation could not be completed due to the following error:

There are no branches to backport to. Aborting.

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 111731

@renshuki
Copy link
Contributor Author

@shainaraskas - looks like the backport failed. Should we backport this manually to other 8.x branches?

@shainaraskas
Copy link
Contributor

@renshuki we don't generally backport to previous 8.x braches, but we backport to the latest major. Don't worry about this backport failing - it was mostly a nice-to-have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport pending >docs General docs changes external-contributor Pull request authored by a developer outside the Elasticsearch team Team:Docs Meta label for docs team v7.17.0 v8.15.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants