-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
cask/audit: fix sharding for font-* casks #17311
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bevanjkay (and @p-linnane for the idea for the original approach!)
@MikeMcQuaid Does this repo allow merging without CI passing, otherwise there's a chicken and egg problem I think? |
We can open a cask rename PR, and then rerun this. |
I have done that, but it fails the audit because it breaks the current rules (before this PR). |
I misunderstood. I thought the plan was to rename those |
It does not. It's perhaps just removing the audit entirely in this PR until after it is merged and fixed here and homebrew-cask. |
This was my understanding, too. If this will fix the issue: let's do that. |
Note, from #17305 (comment) Seems we need to update the docs here, too. |
Is there a specific reason that the tokens need to be adjusted other than to get past the CI issue here? I'm okay if you feel it is too confusing and keep the remane, but I think requiring the usual token standards (Font Finagler.app - remains as |
Yes. We want to make it easier for both contributors and https://github.com/Homebrew/homebrew-linux-fonts
We're already introducing a bunch of exceptions for fonts in the code so it feels no worse to make a one-off exception in the docs, too. |
brew style
with your changes locally?brew typecheck
with your changes locally?brew tests
with your changes locally?The primary issue at hand here is about sharding files, not identifying "font casks", so this PR proposes a change that moves the casks to an appropriate folder solely based on the
token
.We currently don't have any logic that separates a "font cask" from an "application cask", but perhaps we should have a separate audit for new casks that requires the
font-
prefix when a cask only includesfont
artifacts.If we like this route it depends on Homebrew/homebrew-cask#173942