-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Replaced the term "upgraded" with "upgrading" #133138
Conversation
update my branch
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
Pinging @elastic/fleet (Team:Fleet) |
...ins/fleet/public/applications/fleet/sections/agents/components/agent_upgrade_modal/index.tsx
Outdated
Show resolved
Hide resolved
…/components/agent_upgrade_modal/index.tsx Co-authored-by: Nicolas Chaulet <n.chaulet@gmail.com>
Buildkite, test this |
@elasticmachine run elasticsearch-ci/docs |
Buildkite, test this |
@elasticmachine run elasticsearch-ci/docs |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
Thank you. |
Summary
Resolve issue #116742
Summarize your PR. If it involves visual changes include a screenshot or gif.
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers