-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
docs(azure): update azuredevops docs to match new changes #33788
base: main
Are you sure you want to change the base?
docs(azure): update azuredevops docs to match new changes #33788
Conversation
As seen in PR renovatebot#33788 discussion
"packageRules": [ | ||
{ | ||
"matchDatasources": ["azure-pipelines-tasks"], | ||
"extractVersion": "^(?<version>\\d+)" |
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.
What's the reason for this? Are there some characters after which need ignoring?
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.
This comes from the additional information part of the azuredevops docs regarding azure pipeline tasks dependency.
I don't know to what extent we might prefer to use it, link it, or use it for the informations updated ?
…ation and API usage
Co-authored-by: HonkingGoose <[email protected]>
Changes
I wanted to add examples so that new users will benefit from the recent changes related to how renovate picks up tasks version using internal APIs when
azure-pipelines
is enabled in renovate configuration.Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via:
pnpm docs:build
andpnpm mkdocs serve
to preview the documentation changes.Why another PR ?
I made a mistake with my previous PR by committing with the wrong mail, hence the CLA validation did not seem to work fine.
Sorry for the inconvenience.