GitHub links get the name-tag treatment
A GitHub repository link now reads as its owner and repository name, and an issue or pull request link adds the number. The GitHub mark sits in front, and the full URL still comes out when you copy it.
Paste https://github.com/laravel/framework/issues/42 into a commit, a reply or a chat message, and post it. Where you used to get a clipped github.com/laravel/fram…, you now see the GitHub mark and laravel/framework#42. Click it and GitHub opens in a new tab. The link card below is unchanged.
Credit jubianchi, who taught the text renderer to read GitHub addresses. It takes an owner name up to 39 characters and a repository up to 100, and it handles issue and pull request numbers up to 10 digits, so 42 or 9999999999 both work. The screen reader label says whether the number is an issue or a pull request, and 26 GitHub page names, settings and features among them, are left as ordinary URLs.
One catch. Only a bare repository address, an issue or a pull request gets the short form. Link to a file, a commit, a release, a discussion or one comment, or leave a trailing slash or a query string on the end, and the old shortened URL comes back. A number with a leading zero counts as none of the above.