git-annex/Command/Commit.hs

{- git-annex command
 -
 - Copyright 2012 Joey Hess <id@joeyh.name>
 -
 - Licensed under the GNU GPL version 3 or higher.
 -}

module Command.Commit where

import Common.Annex
import Command
import qualified Annex.Branch
import qualified Git

cmd :: [Command]
cmd = [command "commit" paramNothing seek
	SectionPlumbing "commits any staged changes to the git-annex branch"]

seek :: CommandSeek
seek = withNothing start

start :: CommandStart
start = next $ next $ do
	Annex.Branch.commit "update"
	_ <- runhook <=< inRepo $ Git.hookPath "annex-content"
	return True
  where
	runhook (Just hook) = liftIO $ boolSystem hook []
	runhook Nothing = return True
add git-annex-shell commit Eventually, git-annex might try running this after making changes to a remote. I have not yet thought of a good way for it to tell which remotes it needs to run it on though. It can't just do it when shutting down a cached ssh connection, because ssh connection caching is optional, and that would not handle local remotes not accessed over ssh either. 2012-02-25 20:31:38 +00:00			`{- git-annex command`
			`-`
update my email address and homepage url 2015-01-21 16:50:09 +00:00			`- Copyright 2012 Joey Hess <id@joeyh.name>`
add git-annex-shell commit Eventually, git-annex might try running this after making changes to a remote. I have not yet thought of a good way for it to tell which remotes it needs to run it on though. It can't just do it when shutting down a cached ssh connection, because ssh connection caching is optional, and that would not handle local remotes not accessed over ssh either. 2012-02-25 20:31:38 +00:00			`-`
			`- Licensed under the GNU GPL version 3 or higher.`
			`-}`

			`module Command.Commit where`

git-annex-shell: Runs hooks/annex-content after content is received or dropped. 2012-03-14 16:01:56 +00:00			`import Common.Annex`
add git-annex-shell commit Eventually, git-annex might try running this after making changes to a remote. I have not yet thought of a good way for it to tell which remotes it needs to run it on though. It can't just do it when shutting down a cached ssh connection, because ssh connection caching is optional, and that would not handle local remotes not accessed over ssh either. 2012-02-25 20:31:38 +00:00			`import Command`
			`import qualified Annex.Branch`
git-annex-shell: Runs hooks/annex-content after content is received or dropped. 2012-03-14 16:01:56 +00:00			`import qualified Git`
add git-annex-shell commit Eventually, git-annex might try running this after making changes to a remote. I have not yet thought of a good way for it to tell which remotes it needs to run it on though. It can't just do it when shutting down a cached ssh connection, because ssh connection caching is optional, and that would not handle local remotes not accessed over ssh either. 2012-02-25 20:31:38 +00:00
doh't use "def" for command definitions, it conflicts with Data.Default.def 2014-10-14 18:20:10 +00:00			`cmd :: [Command]`
			`cmd = [command "commit" paramNothing seek`
add section metadata to all commands Not yet used .. mindless train work. 2013-03-24 22:28:21 +00:00			`SectionPlumbing "commits any staged changes to the git-annex branch"]`
add git-annex-shell commit Eventually, git-annex might try running this after making changes to a remote. I have not yet thought of a good way for it to tell which remotes it needs to run it on though. It can't just do it when shutting down a cached ssh connection, because ssh connection caching is optional, and that would not handle local remotes not accessed over ssh either. 2012-02-25 20:31:38 +00:00
fix inversion of control in CommandSeek (no behavior changes) I've been disliking how the command seek actions were written for some time, with their inversion of control and ugly workarounds. The last straw to fix it was sync --content, which didn't fit the Annex [CommandStart] interface well at all. I have not yet made it take advantage of the changed interface though. The crucial change, and probably why I didn't do it this way from the beginning, is to make each CommandStart action be run with exceptions caught, and if it fails, increment a failure counter in annex state. So I finally remove the very first code I wrote for git-annex, which was before I had exception handling in the Annex monad, and so ran outside that monad, passing state explicitly as it ran each CommandStart action. This was a real slog from 1 to 5 am. Test suite passes. Memory usage is lower than before, sometimes by a couple of megabytes, and remains constant, even when running in a large repo, and even when repeatedly failing and incrementing the error counter. So no accidental laziness space leaks. Wall clock speed is identical, even in large repos. This commit was sponsored by an anonymous bitcoiner. 2014-01-20 08:11:42 +00:00			`seek :: CommandSeek`
			`seek = withNothing start`
add git-annex-shell commit Eventually, git-annex might try running this after making changes to a remote. I have not yet thought of a good way for it to tell which remotes it needs to run it on though. It can't just do it when shutting down a cached ssh connection, because ssh connection caching is optional, and that would not handle local remotes not accessed over ssh either. 2012-02-25 20:31:38 +00:00
			`start :: CommandStart`
			`start = next $ next $ do`
			`Annex.Branch.commit "update"`
fishy commit 2012-06-14 04:01:48 +00:00			`_ <- runhook <=< inRepo $ Git.hookPath "annex-content"`
ignore hook exit status 2012-03-14 16:39:09 +00:00			`return True`
where indentation 2012-11-12 05:05:04 +00:00			`where`
			`runhook (Just hook) = liftIO $ boolSystem hook []`
			`runhook Nothing = return True`