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

[8.12](backport #3867) Fix formatting in topic about logs explorer #3868

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 7, 2024

An empty line is required or the bulleted list does not render as expected:

image


This is an automatic backport of pull request #3867 done by [Mergify](https://mergify.com).

(cherry picked from commit eec0eb1)

# Conflicts:
#	docs/en/observability/monitor-logs.asciidoc
@mergify mergify bot requested a review from a team as a code owner May 7, 2024 22:26
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels May 7, 2024
Copy link
Contributor Author

mergify bot commented May 7, 2024

Cherry-pick of eec0eb1 has failed:

On branch mergify/bp/8.12/pr-3867
Your branch is up to date with 'origin/8.12'.

You are currently cherry-picking commit eec0eb1f.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/en/observability/monitor-logs.asciidoc

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Copy link
Contributor

github-actions bot commented May 7, 2024

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@dedemorton
Copy link
Contributor

Closing because this should not be backported to 8.12.

@dedemorton dedemorton closed this May 8, 2024
@dedemorton dedemorton deleted the mergify/bp/8.12/pr-3867 branch May 8, 2024 22:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant