Add functionality to link artifacts to work items #377
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #377 +/- ##
=======================================
Coverage ? 91.52%
=======================================
Files ? 13
Lines ? 838
Branches ? 142
=======================================
Hits ? 767
Misses ? 40
Partials ? 31
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
danhellem
reviewed
Aug 1, 2025
There was a problem hiding this comment.
My main comment on this is that the user is going to need to know what the format of the artifact link is. And of course, each type is different. I don't know if there is a good way around this or not. I was hoping we could send the type and then some identifiers to build the uri accordingly. I am okay with giving this a try to start to see how to goes.
…t types and URI construction options
danhellem
approved these changes
Aug 12, 2025
qike-ms
pushed a commit
to qike-ms/azure-devops-mcp
that referenced
this pull request
Aug 12, 2025
Adds a new `wit_add_artifact_link` tool to enable linking work items to repository artifacts (`branches`, `commits`, `pull requests`). ## 🔧 Core Implementation Added `wit_add_artifact_link` tool in [workitems.ts](https://vscode.dev/github/microsoft/azure-devops-mcp/blob/main/src/tools/workitems.ts) ## 📚 Documentation Updated [EXAMPLES.md](https://vscode.dev/github/microsoft/azure-devops-mcp/blob/main/docs/EXAMPLES.md) with new "Adding Artifact Links" section ## ✅ Testing Added test coverage in [workitems.test.ts](https://vscode.dev/github/microsoft/azure-devops-mcp/blob/main/test/src/tools/workitems.test.ts) ## GitHub issue number microsoft#279 ## **Associated Risks** None ## ✅ **PR Checklist** - [x] **I have read the [contribution guidelines](https://github.com/microsoft/azure-devops-mcp/blob/main/CONTRIBUTING.md)** - [x] **I have read the [code of conduct guidelines](https://github.com/microsoft/azure-devops-mcp/blob/main/CODE_OF_CONDUCT.md)** - [x] Title of the pull request is clear and informative. - [x] 👌 Code hygiene - [x] 🔭 Telemetry added, updated, or N/A - [x] 📄 Documentation added, updated, or N/A - [x] 🛡️ Automated tests added, or N/A ## 🧪 **How did you test it?** Run `npm run test` , `npm run build` , `npm run validate-tools` --------- Co-authored-by: Dan Hellem <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a new
wit_add_artifact_linktool to enable linking work items to repository artifacts (branches,commits,pull requests).🔧 Core Implementation
Added
wit_add_artifact_linktool in workitems.ts📚 Documentation
Updated EXAMPLES.md with new "Adding Artifact Links" section
✅ Testing
Added test coverage in workitems.test.ts
GitHub issue number
#279
Associated Risks
None
✅ PR Checklist
🧪 How did you test it?
Run
npm run test,npm run build,npm run validate-tools