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

[Serverless bug bash] Fixes link ref on Install Elastic Defend page (backport #6164) #6228

Closed
wants to merge 2 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 22, 2024

Serverless bug bash

Resolves #6060.

The same fix has been applied to ESS docs.

Previews

Serverless: Install Elastic Defend

ESS: Install Elastic Defend


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

(cherry picked from commit a6c3736)

# Conflicts:
#	docs/serverless/edr-install-config/install-elastic-defend.asciidoc
@mergify mergify bot requested a review from a team as a code owner November 22, 2024 11:57
@mergify mergify bot added the conflicts label Nov 22, 2024
Copy link
Contributor Author

mergify bot commented Nov 22, 2024

Cherry-pick of a6c3736 has failed:

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

You are currently cherry-picking commit a6c37361.
  (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/serverless/edr-install-config/install-elastic-defend.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

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 natasha-moore-elastic self-assigned this Nov 22, 2024
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