May I suggest using Github's releases for ebook files
eshellman opened this issue · comments
advantages
- no filesize limit, repo and ebook files are easier to download
- syncs the files to a git tag
- associates a tag (version number) with the released files
It's likely that there's something I don't understand about git, but I thought I was doing that... Release v5.1
has a corresponding book.epub
in the published
directory. What am I missing?
I don't see how I can associate assets with a release using git
(as opposed to the GitHub
api), so I'll need to change my workflow. I'll look into do that next time. Thanks for the suggestion.
Finally fixed this...