Kris Stern

A summary of the issue at JIRA: https://issues.jenkins.io/browse/JENKINS-54868 So let's compile a list of URLs you are expected to handle with your regex: ``` ssh://[email protected]:22/DefaultCollection/_ssh/elisp ssh://[email protected]/MarkEWaite/tasks.git ssh://git.assembla.com/git-plugin.bin.git https://www.assembla.com/spaces/git-plugin/git-2/ https://markwaite.visualstudio.com/_git/elisp https://markwaite.visualstudio.com/DefaultCollection/_git/elisp...

Yeah, you should have a list of regex patterns you can match against one-by-one. That way you get to catch all of the possible patterns without having one global URL...

Also a request from a user is the following: > it would be helpful to have a global configuration option in the git plugin that would allow the administrator to...

Hi @MarkEWaite I would like to work on this issue for Hacktoberfest.

Thanks so much @MarkEWaite! Sure, I would like a very very brief overview of the architecture of the dev docs, to save me some time prepping for the pull requests....

Also, by dev docs you meant this?: https://www.jenkins.io/doc/developer/

Cool, now I see what I will need to do clearly. Let me start work on this issue soon!

Hi @MarkEWaite I am wondering what is the most efficient way to test out changes in the codebase for the dev docs?

Thanks @MarkEWaite! That's what I have tried as well. Appreciate the details.

Just come up with this, however since I am not yet very familiar with the code base the anchor href are currently hardcoded and not fetched by code iteratively: