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

update: git repo now available. the previous paste expired, sorry about that.

Browse source
This commit is contained in:
anarcat 2018-05-17 18:06:40 +00:00 • committed by admin
parent 78a0bf4814
commit e753c7de4f
1 changed files with 15 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/todo/git-hook_to_sanity-check_git-annex_branch_pushes.mdwn
View file

@ -38,4 +38,18 @@ This might be too limiting for some situations:
Python implementation
---------------------
I started doing an implementation of this in Python here. For technical reasons the git repo is not publicly available, but here's a [dump](http://paste.debian.net/232563/) of the code. I went through what seems to be a rather convoluted process with libgit there because I wanted to have some proper unit tests and generating git commands by hand in a shell script is rather painful.Also, it currently adopts a "blocking" approach, ie. it blocks known problems, but maybe it should be based on an "allow" approach, that is: only allow certain things to go through. So far it only forbids removals and changes to trust.log. A bunch of stuff is still missing like parameters (to allow changing the list of protected files) and checking the log tracking info. Feedback welcome. --[[anarcat]]
I started doing an implementation of this in Python here. The code is
available in [pre-receive-gitannex-check.py](https://gitlab.com/anarcat/puppet-git-annex/raw/a7333fd26af19eb5ee662c261a498c868b8b67e3/files/pre-receive-gitannex-check.py) (permalink, see also
the [latest version](https://gitlab.com/anarcat/puppet-git-annex/blob/master/files/pre-receive-gitannex-check.py)).
I went through what seems to be a rather convoluted design with libgit
because I wanted to have some proper unit tests and generating git
commands by hand in a shell script is rather painful. Also, it
currently adopts a "blocking" approach, ie. it blocks known problems,
but maybe it should be based on an "allow" approach, that is: only
allow certain things to go through.
So far it only forbids removals and changes to trust.log. A bunch of
stuff is still missing like parameters (to allow changing the list of
protected files) and checking the log tracking info. Feedback
welcome. --[[anarcat]]