Why not using attached binaries on release?

adobe-fonts / source-han-code-jp

Source Han Code JP | 源ノ角ゴシック Code

https://ccjktype.fonts.adobe.com/2015/06/source-han-code-jp.html

SIL Open Font License 1.1

1.65k stars 54 forks source link

Why not using attached binaries on release? #7

Closed kakkun61 closed 9 years ago

kakkun61 commented 9 years ago

If you know it and you choose current way on purpose, I'm sorry.

You are using “release” branch to distribute OTF & OTC files and sources are on “master” branch. However you need not to use “release” branch if you use “attach binaries” function on releases.

How to use:

go to edit page of release
drag and drop OTC, OTF files to the area like below
and then users can download the files on release page

attach-binaries

miguelsousa commented 9 years ago

@kakkun61 we know about the "Attach binaries" field. We have the font binaries in a release branch because we want to keep them under version control and because we need access to the font files beyond a download link in the Releases page.