Lasse Fister
Lasse Fister
@m4rc1e could this also be a machine learning application?
https://github.com/googlefonts/fontbakery/issues/2200 https://github.com/googlefonts/fontbakery/issues/2203 https://github.com/googlefonts/fontbakery/issues/2204
Should we add some mild self checks when reading the data.: * expected Columns: `'Status', 'family', 'family name is confirmed as good?', 'upstream', 'fontfiles prefix'` (and maybe more if we...
FIY: about `family name is confirmed as good?` that row is going to be used for a replacement of: **com.google.fonts/check/165** *Familyname must be unique according to namecheck.fontdata.com*
I can confirm that the duplicates for `OK` and `NOTE` are gone and the status typos `NOTe` and `NOE` are gone as well. > When I check the doc history...
Here's more: I'm looking only at git upstreams with status `OK` or `NOTE` now. Generally, for `upstream`, if it is a git repository I'd like to see the url end...
Don't mind the SSL error, it's my problem. It seems like my suspicion was correct. I was able to fetch all these repos with my code, when not trying to...
> No; check 165 is meant to help inform that human decision, but some checks can only be executed by humans, like a final decision if the name is good....
> If you visit https://github.com/googlefonts/literata.git in a browser then it will do the right thing, and likewise if you clone https://github.com/googlefonts/literata it will also work, That's beside the point, the...
> Another col seems better to me "git-branch" ?