Skip to content

Custom Autolinks

Stephan T. Lavavej edited this page Nov 18, 2023 · 17 revisions

This repo supports custom autolinks, which work in GitHub conversations like issues and pull requests, but not the repo's own files. Anyone can use them simply by mentioning a special prefix, followed by a number.

Examples

Pattern Notes Example
CMake-<num> CMake bugs CMake-24249
CWG-<num> Core Working Group issues CWG-2628
DevCom-<num> Developer Community bugs DevCom-724444
LLVM-<num> Pre-GitHub Clang/LLVM/libc++ bugs LLVM-41915
LLVM-D<num> Clang/LLVM/libcxx patches LLVM-D73138
LWG-<num> Library Working Group issues LWG-3080
WG21-N<num> WG21 N-numbered documents WG21-N4190
WG21-P<num> WG21 P-numbered proposals WG21-P1209

GitHub's custom autolink syntax now supports alphanumeric identifiers, so you can cite R-numbered revisions like WG21-P0896R0 or WG21-P0896R4.

Search Engines

You can add custom "search engines" to your browser settings for quickly accessing cited issues.

Search Engine Keyword Query URL
CMake cmake https://gitlab.kitware.com/cmake/cmake/-/issues/%s
Developer Community devcom https://developercommunity.visualstudio.com/t/%s
LLVM Bugs llvm https://llvm.org/PR%s
LWG Issues lwg https://cplusplus.github.io/LWG/issue%s
CWG Issues cwg https://cplusplus.github.io/CWG/issues/%s.html
microsoft/STL gh https://github.com/microsoft/STL/issues/%s
WG21 Papers wg21 https://wg21.link/%s

Then you can type lwg 3080 into your address bar. You can choose arbitrary Search Engine and Keyword names; e.g. you might want to use stl instead of gh.

Microsoft-internal

We also have custom autolinks to Microsoft-internal bugs and pull requests, like VSO-<num>, MSVC-PR-<num>, VS-PR-<num>, OS-<num>, and ArchivedOS-<num>.

Search Engine Keyword Query URL
MSVC PRs msvc-pr https://devdiv.visualstudio.com/DevDiv/_git/msvc/pullrequest/%s
VSO Bugs vso https://devdiv.visualstudio.com/DevDiv/_workitems/edit/%s
VS PRs vs-pr https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequest/%s