-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add tooling to check for HTTPS versions of cask URLs #5804
Comments
Yes, I mass converted some HTTP URLs to HTTPS at one point but didn't save the scripts I used to do so. However, there was a flaw in my method, which is that I didn't detect when HTTPS gets redirected to HTTP. For those cases, it would be better to revert to HTTP. |
I spent a couple of minutes trying to work around the Unfortunately, the code in |
Your call: there are merits either way.
|
Status update: removing state from Should I submit a single PR with all these changes? |
A single PR is fine, though it is better if the PR contains one-commit-per Cask. After a mass change, I usually try to keep a lookout for any user submissions that caught a merge conflict and fix that for the user manually. (Odd that there were still so many – I must have forgotten something in #4967 or #4968.) |
Closing for lack of implementation. This is can be revisited later. |
I saw some cask updates losing their https links and I though we could add a tool to migrate all those casks that have an HTTPS version of the download link (and maybe homepage too) available but are not currently using it.
The text was updated successfully, but these errors were encountered: