`check-vcs-permalinks` - Add support for different branch names
See original GitHub issueNot all repositories use master
for their branch name so it would be great if this hook could support other branch names.
Preferably, this would match any blob link that doesn’t contain a full hash (so only matching 0-f with len of 40 or 64) but if you don’t consider that to be a good solution, then being able to specify a list of branches to match would also work, though it would be a lot more likely to lead to non-permalinks not getting matched.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to view file from different branches side-by-side in VS ...
During step 3, I would often like to see code from the other branch alongside (for example, to see which parameters a certain...
Read more >Working with GitHub Issues in Visual Studio Code
Given how important issues are to our team and other GitHub projects, we wanted to add GitHub issues integration to VS Code.
Read more >How can I refresh remote Git branches?
Hi,There is a new branch in the remote repository, but it does not appear in the branches pop-up. How can I refresh that...
Read more >Visual Studio code editor: Eight tips for using GitLab VS Code
You might also consider using the GitLens: Copy Remote File URL , which even includes the commit SHA in the URL, making it...
Read more >Git: branches in Visual Studio Code - YouTube
https://aka.ms/ vscode -git | Learn all about branch management in Visual Studio Code!#git #github # vscode #visualstudiocode Time Stamps:0:23 ...
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 FreeTop 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
Top GitHub Comments
YAGNI imo
Right now yes, but Git team is making a continuous effort towards SHA256 support (Git 2.29 introduced experimental support for it, I’m not following it that closely to know how far they are with it now) so I figured it might be worth supporting it already since I don’t think it would cause any issues.
That seems fine, do you think it’s worth providing a custom regex option, or is that just an unnecessary complication (until proven it’s actually needed anyway)?
I can look into PRing this if that’s fine with you.