From a33cfd04883ab9822ef51f76e159fc6f97d695c3 Mon Sep 17 00:00:00 2001 From: "https://christian.amsuess.com/chrysn" Date: Fri, 20 Jan 2017 09:49:23 +0000 Subject: [PATCH] add wishlist item --- .../wishlist__58___per-repository_autocommit__61__false.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 doc/todo/wishlist__58___per-repository_autocommit__61__false.mdwn diff --git a/doc/todo/wishlist__58___per-repository_autocommit__61__false.mdwn b/doc/todo/wishlist__58___per-repository_autocommit__61__false.mdwn new file mode 100644 index 0000000000..a71aaa3631 --- /dev/null +++ b/doc/todo/wishlist__58___per-repository_autocommit__61__false.mdwn @@ -0,0 +1,5 @@ +when using git-annex as a minority participant in a repository (eg. because in a hardware project, at some point in time, photos get added), users will start to need to `git annex sync` (because a plain `git pull` / `git push` will work but show errors, and a `pull --all` / `annex merge` is difficult for users to remember). to stay in line with usual git usage, the `sync` must be used with `config annex.autocommit false`, but that needs to be configured on each repository. + +forgetting to do that explicit configuration results, in one sync command, easily results in an unwanted implicit commit that's pushed across remotes. + +could there be a per-repository option (somewhere around .gitattributes, or maybe in the git-annex branch) that disables autocommits for the repository? -- 2.30.2