Import Git Repository with multiple Anki Decks

[gnarlex]

Thank you for your plugin :pray: Makes collaborating to Anki decks much easier :relieved:

One feature that I'm missing is importing multiple decks in a git repository, structured in multiple directories (like in this repository)

github.com/user/university-decks/
├─ foo-deck/
│   ├─ media/
│   └─ deck.json
└─ bar-deck/
   └─ deck.json

At our university we often keep decks in "monorepos" structured like this, because it can be cumbersome to keep many decks in many repositories.

[aplaice]

This sounds like a good idea. (No promises about when this might be implemented, though. :))

---

Ideally, it would be implemented in such a way that it integrates well with export to a git repo with multiple decks (once git export is actually, fully implemented) and possibly snapshotting multiple decks to a single git repo (#115).

[Sparklester]

Why is it not possible as of now to initialize a single git repo for a profile containing several decks separately?

The only thing stopping it is that snapshots automatically add a .git in the folder corresponding to every deck within a profile. This makes manual git handling impossible, since I have to delete the .git in every folder every time before making a commit.

Can the auto git init not be disabled when snapshotting?

[aplaice]

@Sparklester that's a good point!

It seems that Dulwich's git init-equivalent (just like the "real" git init) is perfectly happy to initialise a repo within another repo. We (CrowdAnki) should probably at least get out of the way and not initialise when directly within an existing repo. (i.e. check whether the parent of the deck directory is the root of a git repository and if it is, not initialise — I think there aren't any major edge cases with that (people using git sub-trees?). I'd rather not just check whether we're in a git repository at any level, since people might do crazy things like keep their home folder in git etc.) Ideally, there should be a config option to allow this (single git snapshot repo) without the user having to manually initialise a repo in the root snapshot directory.