1 Remotes configuration API
2 =========================
4 The API in remote.h gives access to the configuration related to
5 remotes. It handles all three configuration mechanisms historically
6 and currently used by Git, and presents the information in a uniform
7 fashion. Note that the code also handles plain URLs without any
8 configuration, giving them just the default information.
15 The user's nickname for the remote
19 An array of all of the url_nr URLs configured for the remote
23 An array of all of the pushurl_nr push URLs configured for the remote
27 An array of refspecs configured for pushing, with
28 push_refspec being the literal strings, and push_refspec_nr
33 An array of refspecs configured for fetching, with
34 fetch_refspec being the literal strings, and fetch_refspec_nr
39 The setting for whether to fetch tags (as a separate rule from
40 the configured refspecs); -1 means never to fetch tags, 0
41 means to auto-follow tags based on the default heuristic, 1
42 means to always auto-follow tags, and 2 means to fetch all
45 `receivepack`, `uploadpack`::
47 The configured helper programs to run on the remote side, for
52 The proxy to use for curl (http, https, ftp, etc.) URLs.
54 struct remotes can be found by name with remote_get(), and iterated
55 through with for_each_remote(). remote_get(NULL) will return the
56 default remote, given the current branch and configuration.
61 A struct refspec holds the parsed interpretation of a refspec. If it
62 will force updates (starts with a '+'), force is true. If it is a
63 pattern (sides end with '*') pattern is true. src and dest are the
64 two sides (including '*' characters if present); if there is only one
65 side, it is src, and dst is NULL; if sides exist but are empty (i.e.,
66 the refspec either starts or ends with ':'), the corresponding side is
69 An array of strings can be parsed into an array of struct refspecs
70 using parse_fetch_refspec() or parse_push_refspec().
72 remote_find_tracking(), given a remote and a struct refspec with
73 either src or dst filled out, will fill out the other such that the
74 result is in the "fetch" specification for the remote (note that this
75 evaluates patterns and returns a single result).
80 Note that this may end up moving to branch.h
82 struct branch holds the configuration for a branch. It can be looked
83 up with branch_get(name) for "refs/heads/{name}", or with
84 branch_get(NULL) for HEAD.
90 The short name of the branch.
94 The full path for the branch ref.
98 The name of the remote listed in the configuration.
102 An array of the "merge" lines in the configuration.
106 An array of the struct refspecs used for the merge lines. That
107 is, merge[i]->dst is a local tracking ref which should be
108 merged into this branch by default.
112 The number of merge configurations
114 branch_has_merge_config() returns true if the given branch has merge
120 There is other stuff in remote.h that is related, in general, to the
121 process of interacting with remotes.