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.x] [Jan 28] GA for third-party response actions (backport #6471) #6489

Merged
merged 3 commits into from
Jan 28, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 28, 2025

Resolves #6397.

Previews

ESS:

Serverless:


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

(cherry picked from commit 285d9d3)

# Conflicts:
#	docs/serverless/endpoint-response-actions/response-actions-config.asciidoc
#	docs/serverless/endpoint-response-actions/third-party-actions.asciidoc
Copy link
Contributor Author

mergify bot commented Jan 28, 2025

Cherry-pick of 285d9d3 has failed:

On branch mergify/bp/8.x/pr-6471
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit 285d9d30.
  (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-config.asciidoc
	modified:   docs/management/admin/third-party-actions.asciidoc

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

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.

@natasha-moore-elastic
Copy link
Contributor

run docs-build

@natasha-moore-elastic natasha-moore-elastic enabled auto-merge (squash) January 28, 2025 18:12
@natasha-moore-elastic natasha-moore-elastic merged commit 4fe3eb2 into 8.x Jan 28, 2025
4 checks passed
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