Skip to content

[8.16] Fix URL to Microsoft page (backport #6830) #6837

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

Merged
merged 3 commits into from
May 7, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 6, 2025

Escapes the double dashes in the URL to this Microsoft page. Previously, the link would 404 when you clicked on it from the HTML output.


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

(cherry picked from commit a7849dd)

# Conflicts:
#	docs/release-notes/8.17.asciidoc
#	docs/release-notes/8.18.asciidoc
@mergify mergify bot added the backport label May 6, 2025
@mergify mergify bot requested a review from a team as a code owner May 6, 2025 19:12
@mergify mergify bot added the conflicts label May 6, 2025
Copy link
Contributor Author

mergify bot commented May 6, 2025

Cherry-pick of a7849dd has failed:

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

You are currently cherry-picking commit a7849ddd.
  (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/release-notes/8.16.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/release-notes/8.17.asciidoc
	deleted by us:   docs/release-notes/8.18.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

github-actions bot commented May 6, 2025

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.

@nastasha-solomon nastasha-solomon merged commit 1b8dd8e into 8.16 May 7, 2025
4 checks passed
@nastasha-solomon nastasha-solomon deleted the mergify/bp/8.16/pr-6830 branch May 7, 2025 15:05
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