summaryrefslogtreecommitdiff
path: root/include/git2/remote.h
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #5336 from libgit2/ethomson/credtypePatrick Steinhardt2020-01-301-1/+1
|\ | | | | cred: change enum to git_credential_t and GIT_CREDENTIAL_*
| * credential: change git_cred to git_credentialethomson/credtypeEdward Thomson2020-01-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We avoid abbreviations where possible; rename git_cred to git_credential. In addition, we have standardized on a trailing `_t` for enum types, instead of using "type" in the name. So `git_credtype_t` has become `git_credential_t` and its members have become `GIT_CREDENTIAL` instead of `GIT_CREDTYPE`. Finally, the source and header files have been renamed to `credential` instead of `cred`. Keep previous name and values as deprecated, and include the new header files from the previous ones.
* | remote functions: return an intEdward Thomson2020-01-241-2/+4
|/ | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* docs: More of itEtienne Samson2019-06-261-1/+2
|
* doc: add missing documentation commentsEtienne Samson2019-06-151-0/+1
|
* Rename opt init functions to `options_init`Edward Thomson2019-06-141-4/+4
| | | | | | | | | | | | | In libgit2 nomenclature, when we need to verb a direct object, we name a function `git_directobject_verb`. Thus, if we need to init an options structure named `git_foo_options`, then the name of the function that does that should be `git_foo_options_init`. The previous names of `git_foo_init_options` is close - it _sounds_ as if it's initializing the options of a `foo`, but in fact `git_foo_options` is its own noun that should be respected. Deprecate the old names; they'll now call directly to the new ones.
* remote: add callback to resolve URLs before connectingErik Aigner2019-05-211-0/+20
| | | | | | Since libssh2 doesn't read host configuration from the config file, this callback can be used to hand over URL resolving to the client without touching the SSH implementation itself.
* remote: Rename git_remote_completion_type to _tethomson/remote_completionEdward Thomson2019-02-251-3/+3
| | | | | For consistency with other "type" enums, rename git_remote_completion_type to git_remote_completion_t.
* remote: rename git_push_transfer_progress callbackEdward Thomson2019-02-221-2/+3
| | | | | | The `git_push_transfer_progress` is a callback and as such should be suffixed with `_cb` for consistency. Rename `git_push_transfer_progress` to `git_push_transfer_progress_cb`.
* indexer: use git_indexer_progress throughoutEdward Thomson2019-02-221-2/+2
| | | | | Update internal usage of `git_transfer_progress` to `git_indexer_progreses`.
* Introduce GIT_CALLBACK macro to enforce cdeclEdward Thomson2019-01-171-5/+5
| | | | | | | | | Since we now always build the library with cdecl calling conventions, our callbacks should be decorated as such so that users will not be able to provide callbacks defined with other calling conventions. The `GIT_CALLBACK` macro will inject the `__cdecl` attribute as appropriate.
* remote: add a flag to prevent generation of the default fetchspecEtienne Samson2018-11-021-0/+3
|
* remote: add a creation flag for ignoring url.insteadOfEtienne Samson2018-11-021-0/+11
|
* remote: provide a generic API for creating remotesEtienne Samson2018-11-021-0/+60
| | | | This supersedes the functionality of remote_create_with_fetchspec, remote_create_anonymous and remote_create_detached.
* push: make the parallelism default follow the docsEtienne Samson2018-08-291-1/+1
|
* docs: standardize comment block for git_*_init_options functionsEtienne Samson2018-05-071-8/+10
|
* remote/proxy: fix git_transport_certificate_check_db commentCarson Howard2018-03-271-2/+2
|
* remote: add typedef to normalize push_update_reference callbackCarson Howard2017-10-061-4/+16
| | | Very many callbacks in libgit2 have some sort of typedef to normalize the name at git_<name_of_operation>_cb. Add a typedef for push_update_references in the remote so the name follows the same conventions.
* remote: add function to create detached remotesEric Myhre2017-05-051-0/+18
| | | | | | | | Right now it is only possible to create remotes from a repository. While this is probably the most common use-case, there are commands which make sense even without a repository, e.g. the equivalence of `git ls-remote`. Add a new function `git_remote_create_detached`, which simply accepts a URL.
* git_remote_push: document that NULL refspecs allowedEdward Thomson2017-05-011-2/+2
|
* Fix typo in remote.h APIRemy Suen2017-03-201-1/+1
|
* Merge pull request #3980 from tiennou/doc-fixesv0.25.0-rc2v0.25.0Carlos Martín Nieto2016-12-201-3/+3
|\ | | | | Documentation fixes
| * remote: fix documentation and indentEtienne Samson2016-11-011-1/+3
| |
| * remote: unused function typedefEtienne Samson2016-11-011-2/+0
| |
* | remote: fix typo in git_fetch_init_options docsJosh Bleecher Snyder2016-12-021-1/+1
|/
* proxy: ask the user for credentials if necessaryCarlos Martín Nieto2016-04-191-3/+16
|
* Add missing ')' to callbacks documentationJosh Junon2016-04-121-1/+1
| | | | | Super minor, but it was bugging me. There was a missing closing paren in the docs.
* Accept custom headers for fetch tooMatt Burke2015-09-101-0/+5
|
* Tell the git_transport about the custom_headersMatt Burke2015-09-081-1/+2
|
* Add custom_headers to git_push_optionsMatt Burke2015-09-081-0/+5
|
* Drop extra_http_headers from git_remoteMatt Burke2015-09-081-3/+0
|
* Allow the world to set HTTP headers for remotesMatt Burke2015-09-041-0/+3
|
* Document git_fetch_options struct and fix typo.Ryan Roden-Corrent2015-07-201-1/+9
| | | | | | | | git_fetch_options was missing from the API docs because it lacked a documentation comment above the struct declaration. I used the git_checkout_options docstring as a template. Also fixes a typo in git_remote_prune_refs (remote, not reamote).
* Rename FALLBACK to UNSPECIFIEDcmn/rename-unspecifiedCarlos Martín Nieto2015-06-251-3/+3
| | | | | Fallback describes the mechanism, while unspecified explains what the user is thinking.
* remote: apply insteadOf configuration.Patrick Steinhardt2015-05-311-0/+6
| | | | | | | | A remote's URLs are now modified according to the url.*.insteadOf and url.*.pushInsteadOf configurations. This allows a user to replace URL prefixes by setting the corresponding keys. E.g. "url.foo.insteadOf = bar" would replace the prefix "bar" with the new prefix "foo".
* Merge pull request #3127 from libgit2/cmn/remote-fixupsCarlos Martín Nieto2015-05-281-32/+6
|\ | | | | Tackle remote API issues from bindings
| * remote: validate refspecs before adding to configCarlos Martín Nieto2015-05-281-2/+2
| | | | | | | | | | | | | | When we moved from acting on the instance to acting on the configuration, we dropped the validation of the passed refspec, which can lead to writing an invalid refspec to the configuration. Bring that validation back.
| * remote: remove fetch parameter from create_anonymousCarlos Martín Nieto2015-05-281-10/+4
| | | | | | | | | | | | An anonymous remote is not configured and cannot therefore have configured refspecs. Remove the parameter which adds this from the constructor.
| * remote: get rid of the run-time refspec settersCarlos Martín Nieto2015-05-171-20/+0
| | | | | | | | | | | | | | | | These were left over from the culling as it's not clear which use-cases might benefit from this. It is not clear that we want to support any use-case which depends on changing the remote's idea of the base refspecs rather than passing in different per-operation refspec list, so remove these functions.
* | Fix error when building as C++.Jason Haslam2015-05-201-1/+1
|/
* remote: remove git_remote_save()Carlos Martín Nieto2015-05-131-15/+2
| | | | | It has now become a no-op, so remove the function and all references to it.
* remote: remove live changing of refspecsCarlos Martín Nieto2015-05-131-19/+12
| | | | | | | | | | | | The base refspecs changing can be a cause of confusion as to what is the current base refspec set and complicate saving the remote's configuration. Change `git_remote_add_{fetch,push}()` to update the configuration instead of an instance. This finally makes `git_remote_save()` a no-op, it will be removed in a later commit.
* remote: move the tagopt setting to the fetch optionsCarlos Martín Nieto2015-05-131-18/+45
| | | | | This is another option which we should not be keeping in the remote, but is specific to each particular operation.
* remote: move the update_fetchhead setting to the optionsCarlos Martín Nieto2015-05-131-18/+9
| | | | | | While this will rarely be different from the default, having it in the remote adds yet another setting it has to keep around and can affect its behaviour. Move it to the options.
* remote: move the transport ctor to the callbacksCarlos Martín Nieto2015-05-131-0/+6
| | | | | | | Instead of having it set in a different place from every other callback, put it the main structure. This removes some state from the remote and makes it behave more like clone, where the constructors are passed via the options.
* remote: add prune option to fetchCarlos Martín Nieto2015-05-131-0/+20
| | | | | Add a prune setting in the fetch options to allow to fall back to the configuration (the default) or to set it on or off.
* remote: remove url and pushurl from the save logicCarlos Martín Nieto2015-05-131-10/+14
| | | | | | As a first step in removing the repository-saving logic, don't allow chaning the url or push url from a remote object, but change the configuration on the configuration immediately.
* Remove the callbacks struct from the remoteCarlos Martín Nieto2015-05-131-98/+183
| | | | | | | | | | | | | | Having the setting be different from calling its actions was not a great idea and made for the sake of the wrong convenience. Instead of that, accept either fetch options, push options or the callbacks when dealing with the remote. The fetch options are currently only the callbacks, but more options will be moved from setters and getters on the remote to the options. This does mean passing the same struct along the different functions but the typical use-case will only call git_remote_fetch() or git_remote_push() and so won't notice much difference.
* push: report the update plan to the callercmn/negotiation-notifyCarlos Martín Nieto2015-04-191-0/+6
| | | | | | | | | It can be useful for the caller to know which update commands will be sent to the server before the packfile is pushed up. git does this via the pre-push hook. We don't have hooks, but as it adds introspection into what is happening, we can add a callback which performs the same function.
* push: remove reflog message overrideCarlos Martín Nieto2015-03-031-6/+5
| | | | We always use "update by push".
View Lorry Controller Status