fonts/nerd-fonts
1
0
Fork 0
mirror of https://github.com/ryanoasis/nerd-fonts.git synced 2024-12-19 20:12:52 +02:00
Code Issues Releases Activity
6fdde00776
nerd-fonts/.gitignore

31 lines
860 B
Plaintext
Raw Normal View History

Added missing Pomicons.otf source file and update .gitignore (fixes #19)
2015-08-05 04:06:17 +02:00
temp-glyph-source-fonts/*
Added gitignore for various WIP stuff
2015-04-22 00:16:00 +02:00
temp/*
Ensure 'Input Mono' never commited per License and Author request
2015-11-11 03:17:15 +02:00
patched-fonts/Input*
gotta-patch-em-all: Add options to simplify patcher testing [why] When working on the font-patcher the developer needs to test the changes on a number of fonts. This is usually a manual call of `font-patcher` and afterwards a 'diff' of the newly created font with the 'old' font in the patched-fonts/ directory with fontforge (which has a font-compare option). If you run gotta-patch-em-all normally the newly generated font will replace the existing font and git will ALWAYS show it as different. The reason is that at least the timestamp in the generated font has changed. Far more easy would be if the new gotta-patch-em-all run could keep the previous timestamps, in that way one can immediately see that the old and new fonts are bitwise equal (via git). Furthermore if you expect a change and want to show the differences of old and new font in fontforge you need both fonts in the filesystem. But a normal gotta-patch-em-all run replaces the font. A different destination folder would help here. [how] Introduce two new (independent) options to a) keep the timestamp equal to previous patch run b) generate the fonts in a different directory While b) is straight forward, a) is a bit more complicated, esp because filenames can change and so on. So the script examines just one (1) random font in the specific font directory and uses its timestamp. In most cases this is correct enough if the developer uses gotta-patch-em-all consequently. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-05 10:23:36 +02:00
check-fonts/*
Ensure 'Input Mono' never commited per License and Author request
2015-11-11 03:17:15 +02:00
unpatched-sample-fonts/Input*
Adds casks and archives to ignore list
2016-11-13 19:22:40 +02:00
casks/*
archives/*
Creates a release asset upload script (WIP) + ignore file where api key will be stored (#32)
2016-11-21 05:34:24 +02:00
private.cfg
Ignores node modules folder
2017-11-18 17:02:22 +02:00
node_modules
Ignores package lock file
2017-11-18 17:00:49 +02:00
# Only apps should have lockfiles
package-lock.json
ignore *.uuid files
2019-09-06 21:44:57 +02:00
# generated *.uuid files
*.uuid
name-parser: Put Python cache files into gitignore Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-08-22 10:28:34 +02:00
bin/scripts/name_parser/__pycache__/*
bin/scripts/name_parser/log
generate-css: Create cheat sheet with removed icons With v3.0.0 we removed some icons and some codepoints have been reused for a different (expanding) set. We want to show the old (removed) icons correctly and the new ones also, so we need the old and the new font for the webpage and reference it accordingly. For the a new style .nfold (read: nd-olf) is introduced and utilized. See pairing commit in the gh-pages branch: Date: Thu May 4 06:01:33 2023 +0200 Update cheat sheet WITH removed icons Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-05-03 17:54:44 +02:00
# This is just needed for the cheat sheet and not go into the repo:
css/nerd-fonts-generated-removed.min.css
Sunset in-repo releases [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>
2023-09-27 10:48:32 +02:00
# AUTOGENERATED lines follow, do not change or remove the comments
IntelOne: Prevent in-repo-release Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-07-26 14:35:43 +02:00
# Non-Repo-Released fonts, see fonts.json:
[ci] Update .gitignore file
2023-11-11 16:49:06 +02:00
patched-fonts/0xProto/*
!patched-fonts/0xProto/README.md
[ci] Update .gitignore file
2023-11-11 16:51:43 +02:00
patched-fonts/GeistMono/*
!patched-fonts/GeistMono/README.md
IntelOne: Prevent in-repo-release Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-07-26 14:35:43 +02:00
patched-fonts/IntelOneMono/*
!patched-fonts/IntelOneMono/README.md
[ci] Update .gitignore file
2023-11-13 13:14:03 +02:00
patched-fonts/IosevkaTermSlab/*
!patched-fonts/IosevkaTermSlab/README.md
[ci] Update .gitignore file
2023-11-13 16:47:40 +02:00
patched-fonts/MartianMono/*
!patched-fonts/MartianMono/README.md
Sunset in-repo releases [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>
2023-09-27 10:48:32 +02:00
# AUTOGENERATED lines end
Reference in New Issue Copy Permalink