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.12] Make the agent upgrade tracking change more obvious and link directly to the docs (backport #826) #827

Merged
merged 1 commit into from
Jan 18, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jan 18, 2024

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


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

… to the docs (#826)

* Highlight agent upgrade details and link to docs.

* Update docs/en/ingest-management/release-notes/release-notes-8.12.asciidoc

Co-authored-by: David Kilfoyle <[email protected]>

---------

Co-authored-by: David Kilfoyle <[email protected]>
(cherry picked from commit 3c38991)
@mergify mergify bot requested a review from a team as a code owner January 18, 2024 16:39
@mergify mergify bot added the backport label Jan 18, 2024
Copy link

A documentation preview will be available soon.

Help us out by validating the Buildkite preview and reporting issues here.
Please also be sure to double check all images to ensure they are correct in the preview.

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.

@cmacknz cmacknz merged commit 5fe6eec into 8.12 Jan 18, 2024
4 checks passed
@cmacknz cmacknz deleted the mergify/bp/8.12/pr-826 branch January 18, 2024 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants