Skip to content

[DOCS] Reformat warning #130697

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

Merged
merged 1 commit into from
Jul 7, 2025
Merged

[DOCS] Reformat warning #130697

merged 1 commit into from
Jul 7, 2025

Conversation

leemthompo
Copy link
Contributor

We should have used the standard warning here because we don't need a title for the admonition

@leemthompo should have caught this in #130691 (comment), but he didn't have enough coffee

We should have used the standard warning here because we don't need a title for the admonition
@leemthompo leemthompo self-assigned this Jul 7, 2025
@leemthompo leemthompo added >docs General docs changes Team:Docs Meta label for docs team auto-backport Automatically create backport pull requests when merged v9.0.0 v9.1.0 labels Jul 7, 2025
Copy link
Contributor

github-actions bot commented Jul 7, 2025

🔍 Preview links for changed docs:

🔔 The preview site may take up to 3 minutes to finish building. These links will become live once it completes.

@elasticsearchmachine
Copy link
Collaborator

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

Copy link
Contributor

github-actions bot commented Jul 7, 2025

🔍 Preview links for changed docs

Copy link
Contributor

@ketkee-aryamane ketkee-aryamane left a comment

Choose a reason for hiding this comment

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

looks good!

@leemthompo leemthompo merged commit ec5254b into main Jul 7, 2025
10 checks passed
@leemthompo leemthompo deleted the leemthompo-patch-6 branch July 7, 2025 09:19
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
9.0 Commit could not be cherrypicked due to conflicts
9.1 Commit could not be cherrypicked due to conflicts

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

leemthompo added a commit to leemthompo/elasticsearch that referenced this pull request Jul 7, 2025
We should have used the standard warning here because we don't need a title for the admonition

(cherry picked from commit ec5254b)

# Conflicts:
#	docs/reference/elasticsearch/mapping-reference/mapping-source-field.md
@leemthompo
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
9.1
9.0

Questions ?

Please refer to the Backport tool documentation

leemthompo added a commit to leemthompo/elasticsearch that referenced this pull request Jul 7, 2025
We should have used the standard warning here because we don't need a title for the admonition

(cherry picked from commit ec5254b)

# Conflicts:
#	docs/reference/elasticsearch/mapping-reference/mapping-source-field.md
elasticsearchmachine pushed a commit that referenced this pull request Jul 7, 2025
We should have used the standard warning here because we don't need a title for the admonition

(cherry picked from commit ec5254b)

# Conflicts:
#	docs/reference/elasticsearch/mapping-reference/mapping-source-field.md
elasticsearchmachine pushed a commit that referenced this pull request Jul 7, 2025
* [DOCS] Reformat warning (#130697)

We should have used the standard warning here because we don't need a title for the admonition

(cherry picked from commit ec5254b)

# Conflicts:
#	docs/reference/elasticsearch/mapping-reference/mapping-source-field.md

* update
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 backport pending >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.

3 participants