Correct parsing of URLs in free-form text

###Summary
Normal online text has conventions for how to enclose URLs so they are
correctly parsed in free-form text. The RFC 3986
[URL:https://tools.ietf.org/html/rfc3986] describes the standard two
(with “[URL:%E2%80%9D%2C%E2%80%9C]”, and with “<”,“>”).

Bitbucket incorrectly parses URLs enclosed in this standard way; see [URL:https://bitbucket.org/wspdigital/benf_wspdigital-boc-my-agent-mobile-web/commits/fb69c40fdc03ea7b99dd5ec135f33a9e2c7f51ed] for an example. The HREF incorrectly includes the enclosing “>”, which makes Bitbucket link to an incorrect URL though the original text was correct.

###Steps to Reproduce

• Push a commit message with [URL:http://....Link....]
• Check the Bitbucket repository commit page

###Expected Results###
It displayed as [URL:http://....Link....]
The hyperlink includes '>' and redirect to http://....Link....>

###Actual Results###
It should be display as ....Link....
The hyperlink will redirect to _http://....Link...._

###Notes###
Please correct the URL parsing to conform to the common conventions (described in RFC 3986) for URLs in the context of free-form text.

###Workaround###
None.

(Suggestions to “remove the markup” do not apply because these are messages written independent of Bitbucket, for a broader audience than Bitbucket, in a standard markup.)