We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This topic comes up every year in discussions so it is worthy of an issue. It can be added to https://googlefonts.github.io/gf-guide/hosting#commits-manage-progress-and-track-changes
Several of us believe we shouldn't be storing font binaries in the repo for the following reasons:
Font binaries should be stored in tagged releases instead.
The text was updated successfully, but these errors were encountered:
@chrissimpkins wdyt
Sorry, something went wrong.
This seems consistent with the guiding principle to "treat fonts like software", provides a clear hook to build SBOMs, ... makes sense to me.
Duplicated, see #43
Agree with this. What needs to change in our tooling to support it?
No branches or pull requests
This topic comes up every year in discussions so it is worthy of an issue. It can be added to https://googlefonts.github.io/gf-guide/hosting#commits-manage-progress-and-track-changes
Several of us believe we shouldn't be storing font binaries in the repo for the following reasons:
Font binaries should be stored in tagged releases instead.
The text was updated successfully, but these errors were encountered: