mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

added annex.commitmessage-command config

Browse source 
Sponsored-by: the NIH-funded NICEMAN (ReproNim TR&D3) project
This commit is contained in:
Joey Hess 2024-02-12 14:34:50 -04:00
parent 66919bf6ec
commit 68e99513f0
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
5 changed files with 36 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/git-annex.mdwn
View file

@ -1088,6 +1088,11 @@ repository, using [[git-annex-config]]. See its man page for a list.)
This works well in combination with annex.alwayscommit=false,
to gather up a set of changes and commit them with a message you specify.
* `annex.commitmessage-command`
This command is run and its output is used as the commit message to the
git-annex branch.
* `annex.alwayscompact`
By default, git-annex compacts data it records in the git-annex branch.

18
doc/todo/make_annex___34__respect__34___.git__47__hooks__47__prepare-commit-msg/comment_6_b8bb9e5c7156e4defd7a2e8b7777e1ba._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 6"""
date="2024-02-12T17:36:32Z"
content="""
Turns out that the assistant doesn't commit to the git-annex branch itself,
instead the pre-commit hook runs `git-annex pre-commit`, and
the git-annex branch commit on process shutdown is where the commit
happens.
A bit surprising! If the pre-commit hook didn't run git-annex,
the assistant would later explicitly commit the branch before
pushing to remotes.
Anyway, this does mean you can rely on the git-annex branch commit
happening after the working tree commit. At least, when there are
no other git-annex processes running.
"""]]