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.8] [ESS] Adds beta tag to D4C (backport #5519) #5528

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 8, 2024

Adds a beta tag to the D4C docs

Previews: CWP overview, get started with CWP


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

(cherry picked from commit 13eaeb0)

# Conflicts:
#	docs/cloud-native-security/d4c-get-started.asciidoc
#	docs/cloud-native-security/d4c-overview.asciidoc
Copy link
Contributor Author

mergify bot commented Jul 8, 2024

Cherry-pick of 13eaeb0 has failed:

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

You are currently cherry-picking commit 13eaeb04.
  (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 <file>..." to mark resolution)
	both modified:   docs/cloud-native-security/d4c-get-started.asciidoc
	both modified:   docs/cloud-native-security/d4c-overview.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

github-actions bot commented Jul 8, 2024

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.

@benironside
Copy link
Contributor

will fix these in a separate PR

@benironside benironside closed this Jul 8, 2024
@mergify mergify bot deleted the mergify/bp/8.8/pr-5519 branch July 8, 2024 17:22
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