blob: a2f346ca710e03a7f5c65574659ac578ab8bf615 [file] [log] [blame]
Junio C Hamano1a4e8412005-12-27 08:17:231git-sh-setup(1)
2===============
3
4NAME
5----
Junio C Hamano01078922006-03-10 00:31:476git-sh-setup - Common git shell script setup code
Junio C Hamano1a4e8412005-12-27 08:17:237
8SYNOPSIS
9--------
Junio C Hamano15567bc2011-07-23 00:51:5910[verse]
Junio C Hamanobb8e9962008-06-30 09:05:0811'. "$(git --exec-path)/git-sh-setup"'
Junio C Hamano1a4e8412005-12-27 08:17:2312
13DESCRIPTION
14-----------
15
Junio C Hamanof9771f62007-01-17 17:42:3016This is not a command the end user would want to run. Ever.
17This documentation is meant for people who are studying the
18Porcelain-ish scripts and/or are writing new ones.
Junio C Hamano1a4e8412005-12-27 08:17:2319
Junio C Hamano1aa40d22010-01-21 17:46:4320The 'git sh-setup' scriptlet is designed to be sourced (using
Junio C Hamanof9771f62007-01-17 17:42:3021`.`) by other shell scripts to set up some variables pointing at
22the normal git directories and a few helper shell functions.
23
24Before sourcing it, your script should set up a few variables;
25`USAGE` (and `LONG_USAGE`, if any) is used to define message
26given by `usage()` shell function. `SUBDIRECTORY_OK` can be set
27if the script can run from a subdirectory of the working tree
28(some commands do not).
29
30The scriptlet sets `GIT_DIR` and `GIT_OBJECT_DIRECTORY` shell
31variables, but does *not* export them to the environment.
32
33FUNCTIONS
34---------
35
36die::
37exit after emitting the supplied error message to the
38standard error stream.
39
40usage::
41die with the usage message.
42
43set_reflog_action::
44set the message that will be recorded to describe the
45end-user action in the reflog, when the script updates a
46ref.
47
Junio C Hamano91baf102007-12-31 09:44:2648git_editor::
49runs an editor of user's choice (GIT_EDITOR, core.editor, VISUAL or
50EDITOR) on a given file, but error out if no editor is specified
51and the terminal is dumb.
52
Junio C Hamanof9771f62007-01-17 17:42:3053is_bare_repository::
54outputs `true` or `false` to the standard output stream
55to indicate if the repository is a bare repository
56(i.e. without an associated working tree).
57
58cd_to_toplevel::
59runs chdir to the toplevel of the working tree.
60
61require_work_tree::
Junio C Hamano90b56532011-05-26 22:39:4962checks if the current directory is within the working tree
63of the repository, and otherwise dies.
64
65require_work_tree_exists::
66checks if the working tree associated with the repository
67exists, and otherwise dies. Often done before calling
68cd_to_toplevel, which is impossible to do if there is no
69working tree.
Junio C Hamanof9771f62007-01-17 17:42:3070
Junio C Hamano91baf102007-12-31 09:44:2671get_author_ident_from_commit::
72outputs code for use with eval to set the GIT_AUTHOR_NAME,
73GIT_AUTHOR_EMAIL and GIT_AUTHOR_DATE variables for a given commit.
74
Junio C Hamano1a4e8412005-12-27 08:17:2375GIT
76---
Junio C Hamanof7c042d2008-06-06 22:50:5377Part of the linkgit:git[1] suite