From 54bae5df37961e7089b9bae736f3d71071ba4ab9 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Mon, 6 Feb 2017 15:32:45 +0000 Subject: [PATCH] initial thoughts --- ...cify_custom_commit_message_for_git-annex_branch_commit.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit.mdwn 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 0000000000..8eac411c1a --- /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]]