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.13] Update setting name in response-actions.asciidoc (backport #5740) #5742

Merged
merged 2 commits into from
Aug 23, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Aug 23, 2024

Follow-up for #5737. More details in this comment.


This is an automatic backport of pull request #5740 done by Mergify.

in both serverless and ESS

(cherry picked from commit 24fafb5)

# Conflicts:
#	docs/serverless/endpoint-response-actions/response-actions.mdx
@mergify mergify bot added the backport label Aug 23, 2024
@mergify mergify bot requested a review from a team as a code owner August 23, 2024 19:43
@mergify mergify bot added the conflicts label Aug 23, 2024
Copy link
Author

mergify bot commented Aug 23, 2024

Cherry-pick of 24fafb5 has failed:

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

You are currently cherry-picking commit 24fafb52.
  (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)

Changes to be committed:
	modified:   docs/management/admin/response-actions.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/endpoint-response-actions/response-actions.mdx

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

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.

@joepeeples joepeeples merged commit 030e4be into 8.13 Aug 23, 2024
3 checks passed
@mergify mergify bot deleted the mergify/bp/8.13/pr-5740 branch August 23, 2024 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant