1GITREMOTE-HELPERS(7) Git Manual GITREMOTE-HELPERS(7)
2
6 gitremote-helpers - Helper programs to interact with remote
7 repositories
8
10 git remote-<transport> <repository> [<URL>]
11
13 Remote helper programs are normally not used directly by end users, but
14 they are invoked by Git when it needs to interact with remote
15 repositories Git does not support natively. A given helper will
16 implement a subset of the capabilities documented here. When Git needs
17 to interact with a repository using a remote helper, it spawns the
18 helper as an independent process, sends commands to the helper’s
19 standard input, and expects results from the helper’s standard output.
20 Because a remote helper runs as an independent process from Git, there
21 is no need to re-link Git to add a new helper, nor any need to link the
22 helper with the implementation of Git.
23 Every helper must support the "capabilities" command, which Git uses to
25 determine what other commands the helper will accept. Those other
26 commands can be used to discover and update remote refs, transport
27 objects between the object database and the remote repository, and
28 update the local object store.
29 Git comes with a "curl" family of remote helpers, that handle various
31 transport protocols, such as git-remote-http, git-remote-https,
32 git-remote-ftp and git-remote-ftps. They implement the capabilities
33 fetch, option, and push.
34
36 Remote helper programs are invoked with one or (optionally) two
37 arguments. The first argument specifies a remote repository as in Git;
38 it is either the name of a configured remote or a URL. The second
39 argument specifies a URL; it is usually of the form
40 <transport>://<address>, but any arbitrary string is possible. The
41 GIT_DIR environment variable is set up for the remote helper and can be
42 used to determine where to store additional data or from which
43 directory to invoke auxiliary Git commands.
44 When Git encounters a URL of the form <transport>://<address>, where
46 <transport> is a protocol that it cannot handle natively, it
47 automatically invokes git remote-<transport> with the full URL as the
48 second argument. If such a URL is encountered directly on the command
49 line, the first argument is the same as the second, and if it is
50 encountered in a configured remote, the first argument is the name of
51 that remote.
52 A URL of the form <transport>::<address> explicitly instructs Git to
54 invoke git remote-<transport> with <address> as the second argument. If
55 such a URL is encountered directly on the command line, the first
56 argument is <address>, and if it is encountered in a configured remote,
57 the first argument is the name of that remote.
58 Additionally, when a configured remote has remote.<name>.vcs set to
60 <transport>, Git explicitly invokes git remote-<transport> with <name>
61 as the first argument. If set, the second argument is
62 remote.<name>.url; otherwise, the second argument is omitted.
63
65 Git sends the remote helper a list of commands on standard input, one
66 per line. The first command is always the capabilities command, in
67 response to which the remote helper must print a list of the
68 capabilities it supports (see below) followed by a blank line. The
69 response to the capabilities command determines what commands Git uses
70 in the remainder of the command stream.
71 The command stream is terminated by a blank line. In some cases
73 (indicated in the documentation of the relevant commands), this blank
74 line is followed by a payload in some other protocol (e.g., the pack
75 protocol), while in others it indicates the end of input.
76 Capabilities
78 Each remote helper is expected to support only a subset of commands.
79 The operations a helper supports are declared to Git in the response to
80 the capabilities command (see COMMANDS, below).
81 In the following, we list all defined capabilities and for each we list
83 which commands a helper with that capability must provide.
84 Capabilities for Pushing
86 connect
87 Can attempt to connect to git receive-pack (for pushing), git
88 upload-pack, etc for communication using git’s native packfile
89 protocol. This requires a bidirectional, full-duplex
90 connection.
91 Supported commands: connect.
93 stateless-connect
95 Experimental; for internal use only. Can attempt to connect to
96 a remote server for communication using git’s wire-protocol
97 version 2. See the documentation for the stateless-connect
98 command for more information.
99 Supported commands: stateless-connect.
101 push
103 Can discover remote refs and push local commits and the history
104 leading up to them to new or existing remote refs.
105 Supported commands: list for-push, push.
107 export
109 Can discover remote refs and push specified objects from a
110 fast-import stream to remote refs.
111 Supported commands: list for-push, export.
113 If a helper advertises connect, Git will use it if possible and
115 fall back to another capability if the helper requests so when
116 connecting (see the connect command under COMMANDS). When choosing
117 between push and export, Git prefers push. Other frontends may have
118 some other order of preference.
119 no-private-update
121 When using the refspec capability, git normally updates the
122 private ref on successful push. This update is disabled when
123 the remote-helper declares the capability no-private-update.
124 Capabilities for Fetching
126 connect
127 Can try to connect to git upload-pack (for fetching), git
128 receive-pack, etc for communication using the Git’s native
129 packfile protocol. This requires a bidirectional, full-duplex
130 connection.
131 Supported commands: connect.
133 stateless-connect
135 Experimental; for internal use only. Can attempt to connect to
136 a remote server for communication using git’s wire-protocol
137 version 2. See the documentation for the stateless-connect
138 command for more information.
139 Supported commands: stateless-connect.
141 fetch
143 Can discover remote refs and transfer objects reachable from
144 them to the local object store.
145 Supported commands: list, fetch.
147 import
149 Can discover remote refs and output objects reachable from them
150 as a stream in fast-import format.
151 Supported commands: list, import.
153 check-connectivity
155 Can guarantee that when a clone is requested, the received pack
156 is self contained and is connected.
157 If a helper advertises connect, Git will use it if possible and
159 fall back to another capability if the helper requests so when
160 connecting (see the connect command under COMMANDS). When choosing
161 between fetch and import, Git prefers fetch. Other frontends may
162 have some other order of preference.
163 Miscellaneous capabilities
165 option
166 For specifying settings like verbosity (how much output to
167 write to stderr) and depth (how much history is wanted in the
168 case of a shallow clone) that affect how other commands are
169 carried out.
170 refspec <refspec>
172 For remote helpers that implement import or export, this
173 capability allows the refs to be constrained to a private
174 namespace, instead of writing to refs/heads or refs/remotes
175 directly. It is recommended that all importers providing the
176 import capability use this. It’s mandatory for export.
177 A helper advertising the capability refspec
179 refs/heads/*:refs/svn/origin/branches/* is saying that, when it
180 is asked to import refs/heads/topic, the stream it outputs will
181 update the refs/svn/origin/branches/topic ref.
182 This capability can be advertised multiple times. The first
184 applicable refspec takes precedence. The left-hand of refspecs
185 advertised with this capability must cover all refs reported by
186 the list command. If no refspec capability is advertised, there
187 is an implied refspec *:*.
188 When writing remote-helpers for decentralized version control
190 systems, it is advised to keep a local copy of the repository
191 to interact with, and to let the private namespace refs point
192 to this local repository, while the refs/remotes namespace is
193 used to track the remote repository.
194 bidi-import
196 This modifies the import capability. The fast-import commands
197 cat-blob and ls can be used by remote-helpers to retrieve
198 information about blobs and trees that already exist in
199 fast-import’s memory. This requires a channel from fast-import
200 to the remote-helper. If it is advertised in addition to
201 "import", Git establishes a pipe from fast-import to the
202 remote-helper’s stdin. It follows that Git and fast-import are
203 both connected to the remote-helper’s stdin. Because Git can
204 send multiple commands to the remote-helper it is required that
205 helpers that use bidi-import buffer all import commands of a
206 batch before sending data to fast-import. This is to prevent
207 mixing commands and fast-import responses on the helper’s
208 stdin.
209 export-marks <file>
211 This modifies the export capability, instructing Git to dump
212 the internal marks table to <file> when complete. For details,
213 read up on --export-marks=<file> in git-fast-export(1).
214 import-marks <file>
216 This modifies the export capability, instructing Git to load
217 the marks specified in <file> before processing any input. For
218 details, read up on --import-marks=<file> in git-fast-
219 export(1).
220 signed-tags
222 This modifies the export capability, instructing Git to pass
223 --signed-tags=verbatim to git-fast-export(1). In the absence of
224 this capability, Git will use --signed-tags=warn-strip.
225
227 Commands are given by the caller on the helper’s standard input, one
228 per line.
229 capabilities
231 Lists the capabilities of the helper, one per line, ending with a
232 blank line. Each capability may be preceded with *, which marks
233 them mandatory for Git versions using the remote helper to
234 understand. Any unknown mandatory capability is a fatal error.
235 Support for this command is mandatory.
237 list
239 Lists the refs, one per line, in the format "<value> <name> [<attr>
240 ...]". The value may be a hex sha1 hash, "@<dest>" for a symref, or
241 "?" to indicate that the helper could not get the value of the ref.
242 A space-separated list of attributes follows the name; unrecognized
243 attributes are ignored. The list ends with a blank line.
244 See REF LIST ATTRIBUTES for a list of currently defined attributes.
246 Supported if the helper has the "fetch" or "import" capability.
248 list for-push
250 Similar to list, except that it is used if and only if the caller
251 wants to the resulting ref list to prepare push commands. A helper
252 supporting both push and fetch can use this to distinguish for
253 which operation the output of list is going to be used, possibly
254 reducing the amount of work that needs to be performed.
255 Supported if the helper has the "push" or "export" capability.
257 option <name> <value>
259 Sets the transport helper option <name> to <value>. Outputs a
260 single line containing one of ok (option successfully set),
261 unsupported (option not recognized) or error <msg> (option <name>
262 is supported but <value> is not valid for it). Options should be
263 set before other commands, and may influence the behavior of those
264 commands.
265 See OPTIONS for a list of currently defined options.
267 Supported if the helper has the "option" capability.
269 fetch <sha1> <name>
271 Fetches the given object, writing the necessary objects to the
272 database. Fetch commands are sent in a batch, one per line,
273 terminated with a blank line. Outputs a single blank line when all
274 fetch commands in the same batch are complete. Only objects which
275 were reported in the output of list with a sha1 may be fetched this
276 way.
277 Optionally may output a lock <file> line indicating the full path
279 of a file under $GIT_DIR/objects/pack which is keeping a pack until
280 refs can be suitably updated. The path must end with .keep. This is
281 a mechanism to name a <pack,idx,keep> tuple by giving only the keep
282 component. The kept pack will not be deleted by a concurrent
283 repack, even though its objects may not be referenced until the
284 fetch completes. The .keep file will be deleted at the conclusion
285 of the fetch.
286 If option check-connectivity is requested, the helper must output
288 connectivity-ok if the clone is self-contained and connected.
289 Supported if the helper has the "fetch" capability.
291 push +<src>:<dst>
293 Pushes the given local <src> commit or branch to the remote branch
294 described by <dst>. A batch sequence of one or more push commands
295 is terminated with a blank line (if there is only one reference to
296 push, a single push command is followed by a blank line). For
297 example, the following would be two batches of push, the first
298 asking the remote-helper to push the local ref master to the remote
299 ref master and the local HEAD to the remote branch, and the second
300 asking to push ref foo to ref bar (forced update requested by the
301 +).
302 push refs/heads/master:refs/heads/master
304 push HEAD:refs/heads/branch
305 \n
306 push +refs/heads/foo:refs/heads/bar
307 \n
308 Zero or more protocol options may be entered after the last push
310 command, before the batch’s terminating blank line.
311 When the push is complete, outputs one or more ok <dst> or error
313 <dst> <why>? lines to indicate success or failure of each pushed
314 ref. The status report output is terminated by a blank line. The
315 option field <why> may be quoted in a C style string if it contains
316 an LF.
317 Supported if the helper has the "push" capability.
319 import <name>
321 Produces a fast-import stream which imports the current value of
322 the named ref. It may additionally import other refs as needed to
323 construct the history efficiently. The script writes to a
324 helper-specific private namespace. The value of the named ref
325 should be written to a location in this namespace derived by
326 applying the refspecs from the "refspec" capability to the name of
327 the ref.
328 Especially useful for interoperability with a foreign versioning
330 system.
331 Just like push, a batch sequence of one or more import is
333 terminated with a blank line. For each batch of import, the remote
334 helper should produce a fast-import stream terminated by a done
335 command.
336 Note that if the bidi-import capability is used the complete batch
338 sequence has to be buffered before starting to send data to
339 fast-import to prevent mixing of commands and fast-import responses
340 on the helper’s stdin.
341 Supported if the helper has the "import" capability.
343 export
345 Instructs the remote helper that any subsequent input is part of a
346 fast-import stream (generated by git fast-export) containing
347 objects which should be pushed to the remote.
348 Especially useful for interoperability with a foreign versioning
350 system.
351 The export-marks and import-marks capabilities, if specified,
353 affect this command in so far as they are passed on to git
354 fast-export, which then will load/store a table of marks for local
355 objects. This can be used to implement for incremental operations.
356 Supported if the helper has the "export" capability.
358 connect <service>
360 Connects to given service. Standard input and standard output of
361 helper are connected to specified service (git prefix is included
362 in service name so e.g. fetching uses git-upload-pack as service)
363 on remote side. Valid replies to this command are empty line
364 (connection established), fallback (no smart transport support,
365 fall back to dumb transports) and just exiting with error message
366 printed (can’t connect, don’t bother trying to fall back). After
367 line feed terminating the positive (empty) response, the output of
368 service starts. After the connection ends, the remote helper exits.
369 Supported if the helper has the "connect" capability.
371 stateless-connect <service>
373 Experimental; for internal use only. Connects to the given remote
374 service for communication using git’s wire-protocol version 2.
375 Valid replies to this command are empty line (connection
376 established), fallback (no smart transport support, fall back to
377 dumb transports) and just exiting with error message printed (can’t
378 connect, don’t bother trying to fall back). After line feed
379 terminating the positive (empty) response, the output of the
380 service starts. Messages (both request and response) must consist
381 of zero or more PKT-LINEs, terminating in a flush packet. The
382 client must not expect the server to store any state in between
383 request-response pairs. After the connection ends, the remote
384 helper exits.
385 Supported if the helper has the "stateless-connect" capability.
387 If a fatal error occurs, the program writes the error message to stderr
389 and exits. The caller should expect that a suitable error message has
390 been printed if the child closes the connection without completing a
391 valid response for the current command.
392 Additional commands may be supported, as may be determined from
394 capabilities reported by the helper.
395
397 The list command produces a list of refs in which each ref may be
398 followed by a list of attributes. The following ref list attributes are
399 defined.
400 unchanged
402 This ref is unchanged since the last import or fetch, although the
403 helper cannot necessarily determine what value that produced.
404
406 The following options are defined and (under suitable circumstances)
407 set by Git if the remote helper has the option capability.
408 option verbosity <n>
410 Changes the verbosity of messages displayed by the helper. A value
411 of 0 for <n> means that processes operate quietly, and the helper
412 produces only error output. 1 is the default level of verbosity,
413 and higher values of <n> correspond to the number of -v flags
414 passed on the command line.
415 option progress {true|false}
417 Enables (or disables) progress messages displayed by the transport
418 helper during a command.
419 option depth <depth>
421 Deepens the history of a shallow repository.
422 'option deepen-since <timestamp>
424 Deepens the history of a shallow repository based on time.
425 'option deepen-not <ref>
427 Deepens the history of a shallow repository excluding ref. Multiple
428 options add up.
429 option deepen-relative {'true|false}
431 Deepens the history of a shallow repository relative to current
432 boundary. Only valid when used with "option depth".
433 option followtags {true|false}
435 If enabled the helper should automatically fetch annotated tag
436 objects if the object the tag points at was transferred during the
437 fetch command. If the tag is not fetched by the helper a second
438 fetch command will usually be sent to ask for the tag specifically.
439 Some helpers may be able to use this option to avoid a second
440 network connection.
441 option dry-run {true|false}: If true, pretend the operation completed
443 successfully, but don’t actually change any repository data. For most
444 helpers this only applies to the push, if supported.
445 option servpath <c-style-quoted-path>
447 Sets service path (--upload-pack, --receive-pack etc.) for next
448 connect. Remote helper may support this option, but must not rely
449 on this option being set before connect request occurs.
450 option check-connectivity {true|false}
452 Request the helper to check connectivity of a clone.
453 option force {true|false}
455 Request the helper to perform a force update. Defaults to false.
456 option cloning {true|false}
458 Notify the helper this is a clone request (i.e. the current
459 repository is guaranteed empty).
460 option update-shallow {true|false}
462 Allow to extend .git/shallow if the new refs require it.
463 option pushcert {true|false}
465 GPG sign pushes.
466 'option push-option <string>
468 Transmit <string> as a push option. As the push option must not
469 contain LF or NUL characters, the string is not encoded.
470 option from-promisor {true|false}
472 Indicate that these objects are being fetched from a promisor.
473 option no-dependents {true|false}
475 Indicate that only the objects wanted need to be fetched, not their
476 dependents.
477 option atomic {true|false}
479 When pushing, request the remote server to update refs in a single
480 atomic transaction. If successful, all refs will be updated, or
481 none will. If the remote side does not support this capability, the
482 push will fail.
483
485 git-remote(1)
486 git-remote-ext(1)
488 git-remote-fd(1)
490 git-fast-import(1)
492
494 Part of the git(1) suite
495Git 2.26.2 2020-04-20 GITREMOTE-HELPERS(7)