-
Notifications
You must be signed in to change notification settings - Fork 324
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
Add update-specs updatecli workflow #3012
Add update-specs updatecli workflow #3012
Conversation
👋 @reakaleek Thanks a lot for your contribution! It may take some time before we review a PR, so even if you don’t see activity for some time, it does not mean that we have forgotten about it. Every once in a while we go through a process of prioritization, after which we are focussing on the tasks that were planned for the upcoming milestone. The prioritization status is typically reflected through the PR labels. It could be pending triage, a candidate for a future milestone, or have a target milestone set to it. |
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.
I don't really have a way to judge it with my current knowledge, but you feeling confident about it is so good enough for me.
What I don't get is what triggers the creation of the PR. What "a dependabot-like experience" means? Is it based on existing vs. latest artifact versions somehow?
Hi @eyalkoren, actually, it's just a cron trigger. Updatecli determines itself if there is a change or not. Dependening on the outcome it creates a PR or not. |
What does this pull request do?
Moves the update specs workflow from apm-server to the consumer using updatecli to have a "dependabot"-like experience.
As a replacement for created PRs like: #2938
How to test
Related issues