GitHub Enterprise Cloud accounts use a slightly different URL scheme,
using org-\d+@github.com instead of git@ or ssh@ (or any of the other
supported variations). This adds support for urls with that format to
the base pattern matching so that users with enterprise cloud accounts
can use vim-rhubarb as expected.
FugitiveFind() is guaranteed to include a Vim friendly path, while
FugitiveCommonDir() currently returns a Git friendly path. That is, the
latter uses forwards slashes even on win32, and might do something to
accommodate Cygwin.
It's possible that vim's built-in will notice the comment lines and set
a filetype of `conf`. This makes using `setfiletype` impractical since
`setfiletype` does not override an already set file type.
Previously if you had a remote in the format:
https://github.com/owner/repo/
When using Gbrowse from fugitive, there would be double slashes in the
opened URL:
https://github.com/owner/repo//blob/master/README.md
This caused GitHub not to show a preview of the lines inline if you
posted it in a comment. This change strips the trailing slash if it
exists.
- `.git/PULLREQ_EDITMSG` is generated by `hub pull-request`.
- `.git/ISSUE_EDITMSG` is generated by `hub issue create`.
- `.git/RELEASE_EDITMSG` is generated by `hub release create`.
I've been holding out on this forever because links to the latest are
occasionally useful, but more often than not, a permanent link to the
file as it currently stands is most useful. At any rate, it shouldn't
be Rhubarb's job to parse out the branch name.
Now that I've actually had time to assess things, it's clear this
parameter is only used as a way to convey the branch name and makes zero
sense. So, it's going to get dropped sooner or later.
