The anki-heimat-flora-fauna from husterknupp

anki-heimat-flora-fauna's People

Contributors

Features

Maybe

Case	Local Changes	Remote Changes	What Happens?
"Share"	x		Import from remote -> run `before-import` script -> no changes in deck.json expected -> export -> expect changes in mediaFiles + notes files -> commit & push changes
"Import"		x	-------------
"Import with local changes"	x	x	❗️ CrowdAnki will remove any changes you did to existing cards in your deck in Anki - before pulling, export your anki deck and run the `after-export` script -> commit changes -> `git pull` -> resolve merge conflict (find out how your vs. remote note) -> push updates -> import other people's updates (See import section in README) - NB: Before pulling is useful so that git can show you the merge conflict, if you already have pulled, git cannot help you here and you have to inspect the git diff closely
"Export with conflicts"	x	x	-------------

CrowdAnki doesn't handle conflicts well. Always look at the diff before commiting. Never push after export right away!

since import overwrites your note changes, export and then pull should be the process when trying to Import (unless you didn't change any note)
import before export is only necessary when you pulled and didn't import the latest changes - exporting an old deck state will then overwrite the latest changes and the git diff will look as if you deleted stuff (which actually you didn't)
(but if you have exported w/o import before, you should look at the git diff closely and commit only hunks that you - the rest of the changes are actually no changes, but a not-up-to-date deck state)

When updates came from remote, don't just export & commit your deck state (import first & then export or inspect the diff closely)

Recommend Projects