Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jul 31, 2025

Contributes to elastic/docs-content#1806.


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

(cherry picked from commit 1633469)

# Conflicts:
#	docs/AI-for-security/connect-to-byo.asciidoc
#	docs/cloud-native-security/cspm-get-started-aws.asciidoc
#	docs/cloud-native-security/kspm-get-started.asciidoc
#	docs/detections/prebuilt-rules/rule-details/multiple-vault-web-credentials-read.asciidoc
#	docs/release-notes/8.16.asciidoc
#	docs/release-notes/8.8.asciidoc
#	docs/release-notes/8.9.asciidoc
@mergify
Copy link
Contributor Author

mergify bot commented Jul 31, 2025

Cherry-pick of 1633469 has failed:

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

You are currently cherry-picking commit 1633469.
  (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/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/AI-for-security/connect-to-byo.asciidoc
	deleted by us:   docs/cloud-native-security/cspm-get-started-aws.asciidoc
	deleted by us:   docs/cloud-native-security/kspm-get-started.asciidoc
	deleted by us:   docs/detections/prebuilt-rules/rule-details/multiple-vault-web-credentials-read.asciidoc
	deleted by us:   docs/release-notes/8.16.asciidoc
	deleted by us:   docs/release-notes/8.8.asciidoc
	deleted by us:   docs/release-notes/8.9.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

@github-actions
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

Closing as none of the updated files exist in the 8.1 branch.

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.

2 participants