| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
git_refdb API fixes
|
| | |
|
| |
| |
| |
| |
| |
| | |
Using an `enum` causes trouble when used with C++ as bitwise operations are not possible w/o casting (e.g., `opts.flags &= ~GIT_BLOB_FILTER_CHECK_FOR_BINARY;` is invalid as there is no `&=` operator for `enum`).
Signed-off-by: Sven Strickroth <email@cs-ware.de>
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Optionally read `.gitattributes` from HEAD
|
| |
| |
| |
| |
| |
| |
| | |
When `GIT_BLOB_FILTER_ATTTRIBUTES_FROM_HEAD` is passed to
`git_blob_filter`, read attributes from `gitattributes` files that
are checked in to the repository at the HEAD revision. This passes
the flag `GIT_FILTER_ATTRIBUTES_FROM_HEAD` to the filter functions.
|
| |
| |
| |
| |
| |
| |
| | |
When `GIT_FILTER_ATTRIBUTES_FROM_HEAD` is specified, configure the
filter to read filter attributes from `gitattributes` files that are
checked in to the repository at the HEAD revision. This passes the flag
`GIT_ATTR_CHECK_INCLUDE_HEAD` to the attribute reading functions.
|
| |
| |
| |
| |
| | |
When `GIT_ATTR_CHECK_INCLUDE_HEAD` is specified, read `gitattribute`
files that are checked into the repository at the HEAD revision.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Introduce `GIT_BLOB_FILTER_NO_SYSTEM_ATTRIBUTES`, which tells
`git_blob_filter` to ignore the system-wide attributes file, usually
`/etc/gitattributes`.
This simply passes the appropriate flag to the attribute loading code.
|
| |
| |
| |
| |
| |
| | |
Allow system-wide attributes (the ones specified in
`/etc/gitattributes`) to be ignored if the flag
`GIT_FILTER_NO_SYSTEM_ATTRIBUTES` is specified.
|
| | |
|
| |
| |
| |
| | |
Users should now use `git_blob_filter`.
|
| |
| |
| |
| |
| | |
Provide a function to filter blobs that allows for more functionality
than the existing `git_blob_filtered_content` function.
|
|\ \
| | |
| | | |
Add sign capability to git_rebase_commit
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Use ci_git_fail_with where appropriate.
Use correct initializer for callback.
|
| | |
| | |
| | |
| | | |
If provided with a null signature, skip adding the signature header and create the commit anyway.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
In the case that we want to build merge + commit, cherrypick + commit, or even just build a commit with signing callback, `git_rebase_commit_signature_cb` particular callback should be made more generic. We also renamed `signature_cb` to `signing_cb` to improve clarity on the purpose of the callback (build a difference between a git_signature and the act of signing).
So we've ended up with `git_commit_signing_cb`.
|
| | |
| | |
| | | |
Reduces the number of callbacks for signing a commit during a rebase operation to just one callback. That callback has 2 out git_buf parameters for signature and signature field. We use git_buf here, because we cannot make any assumptions about the heap allocator a user of the library might be using.
|
| | |
| | |
| | |
| | | |
2 callbacks have been added to git_rebase_options, git_rebase_commit_signature_cb and git_rebase_commit_signature_field_cb. When git_rebase_commit_signature_cb is present in git_rebase_options, it will be called whenever git_rebase_commit is performed, giving an opportunity to sign the commit. The signing procedure can be skipped if the callback specifies passthrough as the error. The git_rebase_commit_signature_field_cb will only be called if the other callback is present or did not passthrough, and it provides means to specify which field a signature is for.
Git_rebase_options was chosen as the home for these callbacks as it keeps backwards compatibility with the current rebase api.
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
In #5118 we remove the double-underscore to make it a normally-named public
function. However, this is not an interesting function outside of the library
and it takes up a name for something that could be more useful.
Remove the single-underscore version as we have not done any releases with it.
|
| | |
|
| |
| |
| |
| |
| | |
`cvar` is an unhelpful name. Refactor its usage to `configmap` for more
clarity.
|
|\ \
| | |
| | | |
More documentation
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For example, https://git-scm.com/docs/gitrepository-layout says:
info
Additional information about the repository is recorded in this directory.
This directory is ignored if $GIT_COMMON_DIR is set
and "$GIT_COMMON_DIR/info" will be used instead.
So when looking for `info/attributes`, we need to check the commondir first,
or fallback to "our" `info/attributes`.
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| | |
We keep the treebuilder entrycount as a `size_t` - return that instead
of downcasting to an `unsigned int`. Callers who were storing this
value in an `unsigned int` will continue to downcast themselves, so
there should be no behavior change for callers.
|
| | |
|
| |
| |
| |
| |
| | |
Our enumeration values are not generally suffixed with `T`. Further,
our enumeration names are generally more descriptive.
|
|\ \
| | |
| | | |
Change API instances of `fromnoun` to `from_noun` (with an underscore)
|
| | |
| | |
| | |
| | |
| | |
| | | |
The majority of functions are named `from_something` (with an
underscore) instead of `fromsomething`. Update the tag function for
consistency with the rest of the library.
|
| | |
| | |
| | |
| | |
| | |
| | | |
The majority of functions are named `from_something` (with an
underscore) instead of `fromsomething`. Update the index functions for
consistency with the rest of the library.
|
| | |
| | |
| | |
| | |
| | |
| | | |
The majority of functions are named `from_something` (with an
underscore) instead of `fromsomething`. Update the blob functions for
consistency with the rest of the library.
|
| | |
| | |
| | |
| | |
| | |
| | | |
The only function that is named `issomething` (without underscore) was
`git_oid_iszero`. Rename it to `git_oid_is_zero` for consistency with
the rest of the library.
|
|/ /
| |
| |
| | |
We don't use double-underscores in the public API.
|
| | |
|
| |
| |
| |
| | |
Docurium seems to choke on this header because it can't see both
git_indexer_progress & git_indexer_progress_cb, let's add the include.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
The trace logging callbacks should match the other callback naming
conventions, using the `_cb` suffix instead of a `_callback` suffix.
|
| |
| |
| |
| |
| | |
The credential callbacks should match the other callback naming
conventions, using the `_cb` suffix instead of a `_callback` suffix.
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The rebase struct stores fields with information about the current
rebase process, which were not accessible via a public interface.
Accessors for getting the `orig_head` and `onto` branch
names and object ids have been added.
|
|\ \
| | |
| | | |
docs: clarify relation of safe and forced checkout strategy
|
| | | |
|
|\ \ \
| | | |
| | | | |
remote: Rename git_remote_completion_type to _t
|