procedure
( git_remote_add_fetchreporemoterefspec)→integer?
repo:repository?remote:string?refspec:string?
Add the given refspec to the fetch list in the configuration. No loaded remote instances will be affected.
procedure
( git_remote_add_pushreporemoterefspec)→integer?
repo:repository?remote:string?refspec:string?
Add the given refspec to the push list in the configuration. No loaded remote instances will be affected.
procedure
directioncallbacksproxy_optsremote:remote?direction:git_directioncallbacks:remote_callbacks?proxy_opts:git_proxy_opts?custom_headers:strarray?
The transport is selected based on the URL. The direction argument is due to a limitation of the git protocol (over TCP or SSH) which starts up a specific binary which can only do the one or the other.
procedure
( git_remote_connectedremote)→boolean?
remote:remote?
Check whether the remote’s underlying transport is connected to the remote host.
repo:repository?url:string?
Create a remote with the given url in-memory. You can use this when you have a URL instead of a remote’s name.
procedure
( git_remote_default_branchoutremote)→integer?
out:buf?remote:remote?
The default branch of a repository is the branch which HEAD points to. If the remote does not support reporting this information directly, it performs the guess as git does; that is, if there are multiple branches which point to the same commit, the first one is chosen. If the master branch is a candidate, it wins.
This function must only be called after connecting.
All remote-tracking branches and configuration settings for the remote will be removed.
procedure
( git_remote_disconnectremote)→void?
remote:remote?
Close the connection to the remote.
procedure
( git_remote_downloadremoterefspecsopts)→integer?
remote:remote?refspecs:strarray?
Connect to the remote if it hasn’t been done yet, negotiate with the remote git which objects are missing, download and index the packfile.
The .idx file will be created and both it and the packfile with be renamed to their final name.
Call git_remote_free to free the data.
procedure
refspecsoptsremote:remote?
Convenience function to connect to a remote, download the data, disconnect and update the remote-tracking branches.
procedure
( git_remote_freeremote)→void?
remote:remote?
This also disconnects from the remote, if the connection has not been closed yet (using git_remote_disconnect).
procedure
array:strarray?remote:remote?
The memory is owned by the user and should be freed with git_strarray_free.
procedure
( git_remote_get_push_refspecsarrayremote)→integer?
array:strarray?remote:remote?
The memory is owned by the user and should be freed with git_strarray_free.
procedure
( git_remote_init_callbacksoptsversion)→integer?
opts:git_remote_callbacks?version:integer?
procedure
( git_remote_listoutrepo)→integer?
out:strarray?repo:repository?
The string array must be freed by the user.
repo:repository?name:string?
The name will be checked for validity. See git_tag_create() for rules about valid names.
procedure
( git_remote_lsremote)→any
remote:remote?
Get the list of references with which the server responds to a new connection.
The remote (or more exactly its transport) must have connected to the remote repository. This list is available as soon as the connection to the remote is initiated and it remains available after disconnecting.
The memory belongs to the remote. The pointer will be valid as long as a new connection is not initiated, but it is recommended that you make a copy in order to make use of the data.
Returns (values (out:(cpointerremote_head?))(size:integer? )). See Multiple Values
procedure
( git_remote_nameremote)→string?
remote:remote?
procedure
( git_remote_pruneremotecallbacks)→integer?
remote:remote?
procedure
( git_remote_prune_refsremote)→integer?
remote:remote?
procedure
( git_remote_pushremoterefspecsopts)→integer?
remote:remote?refspecs:strarray?
Peform all the steps from a push.
procedure
( git_remote_pushurlremote)→string?
remote:remote?
If url.*.pushInsteadOf has been configured for this URL, it will return the modified URL.
procedure
( git_remote_refspec_countremote)→integer?
remote:remote?
All remote-tracking branches and configuration settings for the remote are updated.
The new name will be checked for validity. See git_tag_create() for rules about valid names.
No loaded instances of a the remote with the old name will change their name or their list of refspecs.
procedure
( git_remote_set_autotagreporemotevalue)→integer?
repo:repository?remote:string?value:git_remote_autotag_option_t
The change will be made in the configuration. No loaded remotes will be affected.
procedure
( git_remote_set_pushurlreporemoteurl)→integer?
repo:repository?remote:string?url:string?
Remote objects already in memory will not be affected. This assumes the common case of a single-url remote and will otherwise return an error.
Remote objects already in memory will not be affected. This assumes the common case of a single-url remote and will otherwise return an error.
procedure
( git_remote_stopremote)→void?
remote:remote?
At certain points in its operation, the network code checks whether the operation has been cancelled and if so stops the operation.
procedure
callbacksupdate_fetchheaddownload_tagsremote:remote?callbacks:git_remote_callbacks?update_fetchhead:boolean?download_tags:git_remote_autotag_option_treflog_message:string?
procedure
( git_remote_uploadremoterefspecsopts)→integer?
remote:remote?refspecs:strarray?opts:git_push_options?
Connect to the remote if it hasn’t been done yet, negotiate with the remote git which objects are missing, create a packfile with the missing objects and send it.
procedure
( git_remote_urlremote)→string?
remote:remote?
If url.*.insteadOf has been configured for this URL, it will return the modified URL.