git-annex/doc/git-annex-watch.mdwn

# NAME

git-annex watch - daemon to watch for changes

# SYNOPSIS

git annex watch

# DESCRIPTION

Watches for changes to files in the current directory and its subdirectories,
and takes care of automatically adding new files, as well as dealing with
deleted, copied, and moved files. With this running as a daemon in the
background, you no longer need to manually run git commands when
manipulating your files.
  
By default, all new files in the directory will be added to the repository.
(Including dotfiles.) To block some files from being added, use
`.gitignore` files.
  
By default, all files that are added are added to the annex, the same
as when you run `git annex add`. If you configure annex.largefiles,
files that it does not match will instead be added with `git add`.

# OPTIONS

* `--foreground`

  Avoid forking to the background.

* `--stop`

  Stop a running daemon in the current repository.

* Also the [[git-annex-common-options]](1) can be used.

# SEE ALSO

[[git-annex]](1)

[[git-annex-assistant]](1)

# AUTHOR

Joey Hess <id@joeyh.name>

Warning: Automatically converted into a man page by mdwn2man. Edit with care.
splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00			`# NAME`

git-annex assist assist: New command, which is the same as git-annex sync but with new files added and content transferred by default. (Also this fixes another reversion in git-annex sync, --commit --no-commit, and --message were not enabled, oops.) See added comment for why git-annex assist does commit staged changes elsewhere in the work tree, but only adds files under the cwd. Note that it does not support --no-commit, --no-push, --no-pull like sync does. My thinking is, why should it? If you want that level of control, use git commit, git annex push, git annex pull. Sync only got those options because pull and push were not split out. Sponsored-by: k0ld on Patreon 2023-05-18 18:37:29 +00:00			`git-annex watch - daemon to watch for changes`
splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00
			`# SYNOPSIS`

			`git annex watch`

			`# DESCRIPTION`

			`Watches for changes to files in the current directory and its subdirectories,`
			`and takes care of automatically adding new files, as well as dealing with`
			`deleted, copied, and moved files. With this running as a daemon in the`
			`background, you no longer need to manually run git commands when`
			`manipulating your files.`

improve docs The man pages for these were not really clear that they add new files. 2023-05-17 17:32:47 +00:00			`By default, all new files in the directory will be added to the repository.`
splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00			`(Including dotfiles.) To block some files from being added, use`
			`.gitignore` files.

			`By default, all files that are added are added to the annex, the same`
			as when you run `git annex add`. If you configure annex.largefiles,
			files that it does not match will instead be added with `git add`.

			`# OPTIONS`

			* `--foreground`

			`Avoid forking to the background.`

			* `--stop`

improve --stop docs 2015-05-01 17:41:53 +00:00			`Stop a running daemon in the current repository.`
splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00
split out common options to its own page and mention it on each subcommand page Sometimes users would get confused because an option they were looking for was not mentioned on a subcommand's man page, and they had not noticed that the main git-annex man page had a list of common options. This change lets each subcommand mention the common options, similarly to how the matching options are handled. This commit was sponsored by Svenne Krap on Patreon. 2021-05-10 19:00:13 +00:00			`* Also the [[git-annex-common-options]](1) can be used.`

splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00			`# SEE ALSO`

			`[[git-annex]](1)`

expand manpages cross-references significantly i found that most man pages only had references to the main git-annex manpage, which i stillfind pretty huge and hard to navigate through. i tried to sift through all the man pages and add cross-references between relevant pages. my general rule of thumb is that links should be both ways unless one of the pages is a more general page that would become ridiculously huge if all backlinks would be added (git-annex-preferred-content comes to mind). i have also make the links one per line as this is how it was done in the metadata pages so far. i did everything but the plumbing, utility and test commands, although some of those are linked from the other commands so cross-links were added there as well. 2015-05-29 16:12:55 +00:00			`[[git-annex-assistant]](1)`

splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00			`# AUTHOR`

			`Joey Hess <id@joeyh.name>`

			`Warning: Automatically converted into a man page by mdwn2man. Edit with care.`