-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
chore: rename useUrlParams to useLegacyUrlParams #116062
Conversation
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/uptime (Team:uptime) |
Pinging @elastic/apm-ui (Team:apm) |
Pinging @elastic/fleet (Team:Fleet) |
retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
UX change LGTM
@elasticmachine merge upstream |
Buildkite, test this |
@elasticmachine run elasticsearch-ci/docs |
@elasticmachine merge upstream |
merge conflict between base and head |
⏳ Build in-progress, with failuresFailed CI Steps
To update your PR or re-run it, just comment with: |
⏳ Build in-progress, with failuresFailed CI Steps
To update your PR or re-run it, just comment with: |
⏳ Build in-progress, with failuresFailed CI Steps
To update your PR or re-run it, just comment with: |
⏳ Build in-progress, with failuresFailed CI Steps
To update your PR or re-run it, just comment with: |
⏳ Build in-progress, with failuresFailed CI Steps
To update your PR or re-run it, just comment with: |
⏳ Build in-progress, with failuresFailed CI Steps
To update your PR or re-run it, just comment with: |
⏳ Build in-progress, with failuresFailed CI Steps
To update your PR or re-run it, just comment with: |
💔 Build FailedFailed CI Steps
Metrics [docs]
To update your PR or re-run it, just comment with: |
@elasticmachine merge upstream |
Buildkite, test this |
@elasticmachine run elasticsearch-ci/docs |
⏳ Build in-progress, with failuresFailed CI StepsTo update your PR or re-run it, just comment with: |
💔 Build FailedFailed CI StepsMetrics [docs]
To update your PR or re-run it, just comment with: |
@elasticmachine merge upstream |
Buildkite, test this |
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: |
@luckened Oh wow, I can't believe it took that many retries. I'm embarrassed to be honest but happy to see it merged. |
The following labels were identified as gaps in your version labels and will be added automatically:
If any of these should not be on your pull request, please manually remove them. |
* chore: rename useUrlParams to useLegacyUrlParams * fix: revert uptime & fleet changes Co-authored-by: Kibana Machine <[email protected]>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
@sqren my pleasure to help! thanks for the support ❤️ |
* chore: rename useUrlParams to useLegacyUrlParams * fix: revert uptime & fleet changes Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Lucca Miranda <[email protected]>
Summary
This addresses the other part of #115161 , let me know if i missed something
Checklist
Delete any items that are not applicable to this PR.
For maintainers