mirror of
https://github.com/ryanoasis/nerd-fonts.git
synced 2024-12-19 20:12:52 +02:00
090fbbeebe
[why] We struggle with the pack-committing of patched fonts to the repository on release. This makes our repo grow extremely big. It would be better to just use release artifacts for the releases and not commit any patched font back. There were different approaches discussed, but the problem remains that I personally have no rights to implement anything of that - neither can I force push to the default branch, nor can I create new repos in the organization. [how] To make it still possible to add new fonts without a repo size explosion we do not release NEW fonts back to the repository as commits, but old fonts are handled as before. NEW fonts: * have a new property set in the fonts.yaml 'database' * are released as release artifact via release workflow (but not committed back) * get a readme in the patched_fonts/ directory that points to the release artifact page The solution is not ideal, but for sure better than not adding any fonts anymore or having the repo grow in size faster and faster. At some point in time I would like to phase out all in-repo releases, also for OLD fonts. This scheme has been (manually) used / introduced for Intel One. With this change the .gitignore file is automatically adapted to any new font that is added with the repoRelease flag set to false (which should be the default for any added font from now on). Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de> |
||
|---|---|---|
| .. | ||
| casks.yml | ||
| contributors.yml | ||
| docker-release.yml | ||
| font-patcher.yml | ||
| fontjson.yml | ||
| lock.yml | ||
| packsvgs.yml | ||
| release.yml | ||
| shellcheck.yml | ||
| zip-release.yml | ||