Skip to content
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

feat(azure): link to an existing work item when creating PRs #3542

Merged
merged 1 commit into from
Apr 15, 2019
Merged

feat(azure): link to an existing work item when creating PRs #3542

merged 1 commit into from
Apr 15, 2019

Conversation

JamieMagee
Copy link
Contributor

Looks like I was (happily) wrong about this. There is currently no API to add a work item to a PR as an individual action. Instead you have to link the work item when creating the PR, or by using the updatePullRequest API.

I've tested with the default (0), a non-existent work item ID, and a real work item ID, and they all work with this implementation.

Fixes #3395

@rarkins
Copy link
Collaborator

rarkins commented Apr 15, 2019

What happens if the workItemId is not included in the updatePr request? Does it remain as it was before the PR was updated?

@JamieMagee
Copy link
Contributor Author

Yes, if the updatePr method doesn't contain a property, it's not updated.

@rarkins rarkins merged commit 6ca8991 into renovatebot:master Apr 15, 2019
@rarkins
Copy link
Collaborator

rarkins commented Apr 15, 2019

Thanks again, @JamieMagee. Could your next PR be one to add yourself to the contributors list in package.json? :)
I would add you but your email is hidden

@renovate-bot
Copy link
Collaborator

🎉 This PR is included in version 15.16.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@JamieMagee JamieMagee deleted the azure-work-item branch May 1, 2019 13:50
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Azure - Support linked work items
3 participants