From a8ff96864ea3990982ae91daabc5d550fa4b4b42 Mon Sep 17 00:00:00 2001 From: "jasonb@ab4484d9961a46440958fa1a528e0fc435599057" Date: Sun, 5 Dec 2021 20:37:48 +0000 Subject: [PATCH 1/2] --- .../Use_assistant_to_sync_just_git_repos__63__.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/Use_assistant_to_sync_just_git_repos__63__.mdwn diff --git a/doc/forum/Use_assistant_to_sync_just_git_repos__63__.mdwn b/doc/forum/Use_assistant_to_sync_just_git_repos__63__.mdwn new file mode 100644 index 0000000000..db4efbbe1b --- /dev/null +++ b/doc/forum/Use_assistant_to_sync_just_git_repos__63__.mdwn @@ -0,0 +1,11 @@ +Hi, + +So lately I've been using git-annex to sync repos with only markdown files for Obsidian. Running `git annex sync --no-content` works well for this. But I have to remember when I've updated my Obsidian files on one system and make sure to sync to other repos. + +Could I use the assistant for this? For repos with annexed files, I've always preferred to manually manage my repos, so I've never used the assistant. + +Ideally, as I commit changes, it tries to sync them to other systems, and if those systems are offline (my MBP is closed for example and the ssh connection therefore times out), nothing explodes. + +Is this possible? Is it possible with a half dozen similar repos? Can a single agent do this or do I need to start one for each repo? + +Thanks! From 371238eca383d384cae3d5085e02cb97192bd1d1 Mon Sep 17 00:00:00 2001 From: alt Date: Mon, 6 Dec 2021 15:56:56 +0000 Subject: [PATCH 2/2] --- doc/forum/conflict_with_git-crypt.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/forum/conflict_with_git-crypt.mdwn diff --git a/doc/forum/conflict_with_git-crypt.mdwn b/doc/forum/conflict_with_git-crypt.mdwn new file mode 100644 index 0000000000..0484ea5c87 --- /dev/null +++ b/doc/forum/conflict_with_git-crypt.mdwn @@ -0,0 +1,3 @@ +[git-crypt](https://www.agwa.name/projects/git-crypt/) is executed as a filter for secrets specified in `.gitattributes` files. However, git-annex initialization results in `* filter=annex` being added to `$GIT_DIR/info/attributes`, which [has the highest precedence](https://www.git-scm.com/docs/gitattributes#_description), ultimately causing any git-crypt filtering to be bypassed. + +Is there a recommended workaround for this? Thanks!