Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Nov 22, 2024

Serverless bug bash

Resolves #6016 by updating the cases API links to lead to the API reference site.

The same fix has been applied to ESS docs.

Previews

Serverless:

ESS:


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

* Updates cases API link

* replaces link

(cherry picked from commit 115cbe6)

# Conflicts:
#	docs/serverless/alerts/signals-to-cases.asciidoc
#	docs/serverless/investigate/cases-open-manage.asciidoc
#	docs/serverless/investigate/cases-overview.asciidoc
@mergify mergify bot added the conflicts label Nov 22, 2024
@mergify mergify bot requested a review from a team as a code owner November 22, 2024 11:56
@mergify
Copy link
Contributor Author

mergify bot commented Nov 22, 2024

Cherry-pick of 115cbe6 has failed:

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

You are currently cherry-picking commit 115cbe6e.
  (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/cases/cases-manage.asciidoc
	modified:   docs/cases/cases-overview.asciidoc
	modified:   docs/detections/alerts-add-to-cases.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/alerts/signals-to-cases.asciidoc
	deleted by us:   docs/serverless/investigate/cases-open-manage.asciidoc
	deleted by us:   docs/serverless/investigate/cases-overview.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

@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 natasha-moore-elastic self-assigned this Nov 22, 2024
@natasha-moore-elastic natasha-moore-elastic merged commit 2bc4d3f into 8.17 Nov 22, 2024
3 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.

2 participants