You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 8, 2023. It is now read-only.
Some projects don't host their font project repositories originally on GitHub. E.g. SMC host on GitLab and merely mirror to GitHub. Hence, the projects live on GitLab, so do issue trackers etc. I wonder if we should accept other hosts for projects. This could make tooling more complicated when automation expects the GitHub API to be available, e.g. could be when downloading attachments from tag releases (I'll file an issue for this in googlefonts/gftools#230).
Some projects don't host their font project repositories originally on GitHub. E.g. SMC host on GitLab and merely mirror to GitHub. Hence, the projects live on GitLab, so do issue trackers etc. I wonder if we should accept other hosts for projects. This could make tooling more complicated when automation expects the GitHub API to be available, e.g. could be when downloading attachments from tag releases (I'll file an issue for this in googlefonts/gftools#230).
For an introduction see also googlefonts/gftools#231
If we have a
https://
url to the git repository, that works withgit clone
, this actually works already ingftools packager
e.g. inupstream.yaml
can also be
and the result will be the same.
The text was updated successfully, but these errors were encountered: