Closed jsumnerp closed 4 years ago
azureWorkItemId
needs to be configured in the "bot" config, not the renovate.json
. Cc @JamieMagee as I'm not sure if this was done intentionally or not, or if we should re-implement to support repo-side config.
Yes, I think whoever wrote the feature for themselves must have been configuring it in their global bot config rather than per-repo.
Yes, I think whoever wrote the feature for themselves must have been configuring it in their global bot config rather than per-repo.
Yeah, I wonder who that could have been 🙄
I should just set the stage
to repository
in the definition for the config?
Haha I thought it was someone else.
That won't solve it I think, because it's passed in initRepo which is prior to renovate.json retrieval. Would need to be parsed in createPr and maybe more
This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon if no further activity occurs.
I've moved this issue to the renovate repo, as it does appear to be a bug with renovate and not just a config issue.
As a workaround you can add --azure-work-item-id=6777
to the Additional args for the RenovateMe task, where 6777 is the actual work item number you want.
:tada: This issue has been resolved in version 23.19.1 :tada:
The release is available on:
23.19.1
Your semantic-release bot :package::rocket:
What Renovate type are you using? https://marketplace.visualstudio.com/items?itemName=jyc.vsts-extensions-renovate-me&ssr=false#overview
Describe the bug Renovate is not linking the pull requests it creates to the azure work item
Is the config being used
Relevant debug logs
To Reproduce
azure-pipelines.yml
package.json
Additional context
Not sure if this is a problem with renovate or the azure devops plugin renovate me