git-annex-remote-git-aafs
radicle-migration-tool
| git-annex-remote-git-aafs | radicle-migration-tool | |
|---|---|---|
| 1 | 2 | |
| 1 | 8 | |
| - | - | |
| - | 9.1 | |
| about 5 years ago | 8 days ago | |
| Perl | Java | |
| - | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
git-annex-remote-git-aafs
-
Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
You can already use it with git-annex to store binaries using the git-annex-remote-git-aafs[1] special remote.
Although I would be careful and make sure you understand what it is doing to your branch namespace. Even though in the worst case it would not save any space over directly committing binaries, they are in orphan branches that can be pruned without rewriting history.
But even so, you can just use any number of git-annex special remotes to bypass using git for sharing files.
They may eventually add first-party support for git-annex. But nothing is stopping you from using it now.
[1]: https://github.com/domo141/git-annex-remote-git-aafs
radicle-migration-tool
-
Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
In addition, in order to migrate your GitHub issues to Radicle (which the above doesn't cover), there's this command-line tool [1] that should get you most - if not all - of the way there.
Migrating GitHub Pull Requests (PRs) to Radicle Patches is somewhat more involved, but that should still be possible (even if it involves some loss of information along the way, due to potential schema mismatches) ...
[1] - https://github.com/cytechmobile/radicle-github-migrate
What are some alternatives?
Pi-hole - A black hole for Internet advertisements