Open
Conversation
Owner
|
F |
Owner
|
will take a look over the next few days - thanks for the submission @mikkurogue ! |
Author
|
No worries bud, I'm gonna try and take out some time during the day at work as well to figure out the comment stacking referencing the ADO work items, see if theres an elegant way to figure out what provider is being used and if comment formatting can be applied for ADO (or not, Azure Devops isn't exactly the hottest platform in town) |
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
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 Azure Devops integration, mostly cause I want to use ryu at work and we sadly use devops (F in the chat boys).
I'm opening this, but I'd rather do some testing still (theres some ADO specific issues with PR's and the stack comment linking work items from the platform, which in many cases wont be equal to the created PR number so I also want to discuss the idea of then adding backticks for azure specific ops to wrap the PR number in something that wont be picked up as an in-platform link to some (potentially non-existent) work item number (like in our case, we use jira too for that) or that the work items aren't in sync with the PR's (which I'd like to assume is going to always be the case)
Let me know thoughts, and send prayers for me having to use ADO daily
Edit;
also my first major check in on how claude works, and I probably messed up alot, just adding this for transparency.