summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar yarikoptic <yarikoptic@web>2017-02-06 15:32:45 +0000
committerGravatar admin <admin@branchable.com>2017-02-06 15:32:45 +0000
commitcae2699bc8c3106e51665c53ce8ff8e84272e190 (patch)
treee7d814d8ec28f137ff5ce44ea77856aaf6919bcd /doc
parentf026f717b35c94bdb70e4948b80d49c8c467701f (diff)
initial thoughts
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit.mdwn b/doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit.mdwn
new file mode 100644
index 000000000..8eac411c1
--- /dev/null
+++ b/doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit.mdwn
@@ -0,0 +1,3 @@
+ATM many commit messages in git-annex branch are just an "update". But I wondered if it could be relatively simple to implement to be able to provide a custom commit message, e.g. by defining some environment variable (e.g. GIT_ANNEX_UPDATE_MESSAGE) during whatever process is initiating the actual commit? sure thing there could be cases whenever multiple processes "contributed" to the changes which are finally "flushed" by committing, but imho it could provide a good way to annotate changes within git-annex branch at least to some degree. E.g. I could use "update: added URLs to the files for datalad-archives remote" ;)
+
+[[!meta author=yoh]]