Started the new year by pushing a bunch of commits to #github, when I got the dreaded warning about commit file size:
remote: warning: File ... is larger than GitHub's recommended maximum file size of 50.00 MB.
The recommended solution is to use #gitlfs, but having been burned by it in the past, I know Git LFS is the spawn of the devil.
So looking for an alternative, I came upon #gitannex.
Will try that on an experimental basis to see if it works.
https://git-annex.branchable.com
=> More informations about this toot | More toots from sumanthvepa@mastodon.social
@sumanthvepa I've been using git annex
since before git lfs
existed (literally, and by quite some years) and it just keeps getting better. Lack of forge support is probably the only real drawback, but given the repo can live on forges even without support and the annex data passed around other ways it has never been a blocker.
=> More informations about this toot | More toots from alerque@mastodon.social
@alerque @sumanthvepa Nowadays you can rather easily host a forgejo with git annex support, which is just marvellous! 👌
https://blog.datalad.org/posts/forgejo-aneksajo/
https://blog.datalad.org/posts/forgejo-aneksajo-large-datasets/
=> More informations about this toot | More toots from nobodyinperson@fosstodon.org
@nobodyinperson @alerque Looks cool. Will check it out. Thank you.
=> More informations about this toot | More toots from sumanthvepa@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini