Support permalinks from a git tag
See original GitHub issueWhen trying to create a permalink for https://github.dev/python/cpython/blob/v3.8.12/Objects/typeobject.c#L921 (note the v3.8.12 tag), I get the following message:
On github.com I can create the link without issue, so I would love to be able to do the same from github.dev .
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Getting permanent links to files - GitHub Docs
Press Y to permalink to a file in a specific commit. For a permanent link to the specific version of a file that...
Read more >Using Permalinks – WordPress.org Forums
Permalinks help to create a URL structure that is easy for both humans and search engines to understand and share. A permalink is...
Read more >git-tag Documentation - Git
git -tag - Create, list, delete or verify a tag object signed with GPG ... Also supports "version:refname" or "v:refname" (tag names are...
Read more >How to link to a specific line number on GitHub - Stack Overflow
Select a line by clicking on the line number or select multiple lines by downholding Shift (the same as how you select multiple...
Read more >A Tutorial for Tagging Releases in Git - DEV Community
Use the command whenever you want to list all the existing tags, or you could filter the list with git tag -l 'v1.1.*'...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Running GHPRI out of sources against latest RemoteHub and can confirm that GHPRI permalink generation now works when opening the following GitHub urls in RemoteHub (previously, if you had any of these open, permalink generation did not work):
(The tag urls didn’t work because no upstream was found and the repository metadata HEAD commit was wrong; the commit urls didn’t work because no upstream was found.)
This is because RemoteHub caches metadata on disk and doesn’t invalidate that cache appropriately. I have pushed a fix in RemoteHub to ignore cached metadata and ask for the latest info from network when first initializing the repo. Users who have already seen the bad metadata once like @brettcannon should just be able to update RemoteHub and reload.