blitz-gg 2.1.165 (new cask) #174573
Merged
blitz-gg 2.1.165 (new cask) #174573
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PythonCoderAS
force-pushed
the
add-blitzgg
branch
from
b40e016
to
01ea538
Compare
miccal
reviewed
May 23, 2024
miccal
reviewed
May 23, 2024
|
Suggested changes based on the following:
|
|
miccal
added
the
awaiting maintainer feedback
|
Would be fine with |
blitz 2.1.165 (new cask) Co-authored-by: Miccal Matthews <miccal.matthews@gmail.com> Co-authored-by: Miccal Matthews <miccal.matthews@gmail.com>
miccal
removed
the
awaiting maintainer feedback
miccal
approved these changes
May 26, 2024
p-linnane
approved these changes
May 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.
In the following questions
<cask>is the token of the cask you're submitting.After making any changes to a cask, existing or new, verify:
brew audit --cask --online <cask>is error-free.brew style --fix <cask>reports no offenses.Additionally, if adding a new cask:
brew audit --cask --new <cask>worked successfully.HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask>worked successfully.brew uninstall --cask <cask>worked successfully.It seems that the cask existed but at some point they changed a bunch of the subdomain names, and was removed in #138248.