GitHub branch redirects appear to fail
See original GitHub issueGitHub allows for branch redirects (for example, for projects that rename their default branch from master
to main
). The tool doesn’t appear to follow these redirects, so license text fetching can fail.
I’m happy to submit a PR with a fix, if the desired behavior is that such redirects are followed by default.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Redirects for moved repos don't seem to work · Issue #467
I have a repo that was moved, and I can't create a pull request to it. I have a branch pushed to origin...
Read more >Release's download URL is redirecting #46420
So the Github download URl seems to redirect somewhere. The URL itself is working as it suppose to, you are able to download...
Read more >error with branch upstream/master · Issue #5181 · desktop ...
In the background the app periodically checks if there are new commits on the default branch, and if so the blue dot appears...
Read more >git - What does the warning "redirecting to" actually mean?
"Slight" means that it is there, but it can be fixed automatically, so Git doesn't give an error, but rather a warning.
Read more >Too many redirects or authentication replays error when Git ...
The UI and API seem unable to set new credentials if the existing ... Please check the URL, default branch name, and authentication...
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
@AaronFeickert, You are right pull request #62 doesn’t fix this issue. The https://github.com/tomchavakis/nuget-license/pull/61 is working only if you use the flag export-license-texts in case that you want to have all the licenses in text files. Unfortunately, there are other cases with other licenses that instead of text the output is HTML. I’ll try to fix it asap.
@AaronFeickert , I’ll close this issue which resolved with this PR: https://github.com/tomchavakis/nuget-license/pull/63