-
Notifications
You must be signed in to change notification settings - Fork 497
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
🌱 add support for parsing azure devops urls #4178
Conversation
a3cf3e4
to
f17ce4c
Compare
f17ce4c
to
f2a8e13
Compare
f2a8e13
to
82c79b3
Compare
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.
Mostly looks good, just one comment.
This pull request has been marked stale because it has been open for 10 days with no activity |
82c79b3
to
c449f28
Compare
c449f28
to
82af7f1
Compare
82af7f1
to
0db17fd
Compare
This pull request has been marked stale because it has been open for 10 days with no activity |
@raghavkaul If I've addressed all your comments, could you merge this please? |
0db17fd
to
8f9e690
Compare
Signed-off-by: Jamie Magee <jamie.magee@gmail.com>
8f9e690
to
6a95b4b
Compare
What kind of change does this PR introduce?
Initial part of feature #4177.
Mainly to see if the overall feature would be accepted and if I am following the contribution guidelines correctly, before I put a lot of work into the rest of the implementation.
What is the current behavior?
N/A
What is the new behavior (if this is a feature change)?**
Azure DevOps URLs can now be parsed
Which issue(s) this PR fixes
Initial part of #4177
Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)