| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Test that we can properly abort a rebase when it is initialized by a
revspec. This ensures that we do not conflate revspecs and refnames.
|
| |\
| |
| | |
Allow creating copies of `git_reference` objects.
|
| | | |
|
| |\ \
| | |
| | | |
Rebase improvements with IDs
|
| | | |
| | |
| | |
| | |
| | | |
When rebasing with IDs, we do not return to the `branch`,
we remain in a detached HEAD state.
|
| | |/
| |
| |
| |
| | |
Instead of `open`ing a rebase and `abort`ing that, test that we can
`abort` a rebase that has just begun with `init`.
|
| | |
| |
| |
| |
| |
| |
| | |
While no extra header fields are defined for tags, git accepts them by
ignoring them and continuing the search for the message. There are a few
tags like this in the wild which git parses just fine, so we should do
the same.
|
| |/ |
|
| |\
| |
| | |
Proxy configuration
|
| | |
| |
| |
| |
| |
| | |
We leave this up to the scheme in the url field. The type should only
tell us about whether we want a proxy and whether we want to auto-detect
it.
|
| | |
| |
| |
| |
| |
| | |
When we're dealing with proxy addresses, we only want a hostname and
port, and the user would not provide a path, so make it optional so we
can use this same function to parse git as well as proxy URLs.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In order to match the star-star, we disable the flag that's looking for
a single path element, but that leads to searching for the pattern in
the middle of elements in the input string.
Mark when we're handing a star-star so we jump over the elements in our
attempt to match the part of the pattern that comes after the star-star.
While here, tighten up the check so we don't allow invalid rules
through.
|
| |/ |
|
| |
|
|
|
|
| |
When running as root, skip the unreadable file tests, because, well,
they're probably _not_ unreadable to root unless you've got some
crazy NSA clearance-level honoring operating system shit going on.
|
| |\
| |
| | |
refs: provide a more general error message for dwim
|
| | |
| |
| |
| |
| |
| |
| | |
If we cannot dwim the input, set the error message to be explicit about
that. Otherwise we leave the error for the last failed lookup, which
can be rather unexpected as it mentions a remote when the user thought
they were trying to look up a branch.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
When we turned strict object creation validation on by default, we
forgot to inform the refs::create tests of this. They, in fact,
believed that strict object creation was off by default. As a result,
their cleanup function went and turned strict object creation off for
the remaining tests.
|
| |/
|
|
| |
This lets us run with strict object creation on.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When passing -DUSE_OPENSSL:BOOL=OFF to cmake the testsuite will
fail with the following error:
core::stream::register_tls [/tmp/libgit2/tests/core/stream.c:40]
Function call failed: (error)
error -1 - <no message>
Fix test to assume failure for tls when built without openssl.
While at it also fix GIT_WIN32 cpp to check if it's defined
or not.
|
| |\
| |
| | |
iterator/diff: allow trailing `/` on start/end paths to match submodules
|
| | |
| |
| |
| |
| |
| | |
Allow callers to specify a start path with a trailing slash to match
a submodule, instead of just a directory. This is for some legacy
behavior that's sort of dumb, but there it is.
|
| | |
| |
| |
| |
| | |
Test that submodules are found when the are included in a pathspec
but have a trailing slash.
|
| |/
|
|
|
|
| |
If we're looking for a symlink, realpath will give us the resolved path,
which is not what we're after, but a canonicalized version of the path
the user asked for.
|
| |\
| |
| | |
WD iterator: properly identify submodules
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| | |
config: don't write duplicate section
|
| | | |
|
| | |
| |
| |
| |
| | |
We should notice that we are in the correct section to add. This is a
cosmetic bug, since replacing any of these settings does work.
|
| |\ \
| |/
|/| |
config: don't special-case multivars that don't exist yet
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This special-casing ignores that we might have a locked file, so the
hashtable does not represent the contents of the file we want to
write. This causes multivar writes to overwrite entries instead of add
to them when under lock.
There is no need for this as the normal code-path will write to the file
just fine, so simply get rid of it.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
(It's slow!)
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Iterator tests were split over repo::iterator and diff::iterator,
with duplication between the two. Move them to iterator::index,
iterator::tree, and iterator::workdir.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Prior iterator implementations returned `GIT_ENOTFOUND` when
trying to advance into empty directories. Ensure that we no longer
do that and simply handle them gracefully.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
tree_iterator was only working properly for a pathlist containing
file paths. In case of directory paths, it didn't match children
which contradicts GIT_DIFF_DISABLE_PATHSPEC_MATCH and
is different from index_iterator and fs_iterator.
As a consequence head-to-index status reporting for a specific
directory did not work properly -- all files have been reported
as added.
Include additional tests.
|
| | | |
|
| | |
| |
| |
| |
| | |
`git_iterator_advance_over` is a gnarly bit of code with no actual
tests.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
In the workdir iterator we do some tricky things to step down into
directories to look for things that are in our pathlist. Make sure
that we don't confuse between folders that we're definitely going to
return everything in and folders that we're only stepping down into
to keep looking for matches.
|
| | |
| |
| |
| |
| | |
Ensure that when specifying start/end paths, or pathlists, that we
deal correctly with submodules.
|
| | |
| |
| |
| |
| | |
Expand the workdir tests to validate the paths in case sensitive
and insensitive tests.
|