summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #3109 from libgit2/cmn/index-use-diffEdward Thomson2015-05-191-0/+13
|\ | | | | Use a diff for iteration in index_update_all and index_add_all
| * index: include TYPECHANGE in the diffCarlos Martín Nieto2015-05-141-0/+13
| | | | | | | | Without this option, we would not be able to catch exec bit changes.
* | push: add tests for the push negotiation callbackCarlos Martín Nieto2015-05-141-0/+114
|/ | | | | The functionality was meged without including tests, so let's add them now.
* Merge pull request #3119 from ethomson/ignoreCarlos Martín Nieto2015-05-131-1/+62
|\ | | | | Attributes: don't match files for folders
| * attr tests: make explicit our dir/file match testsEdward Thomson2015-05-131-12/+24
| |
| * attr test: test a file beneath ignored folderEdward Thomson2015-05-121-1/+1
| |
| * attr: test that a file is not ignored for a folderEdward Thomson2015-05-121-0/+17
| | | | | | | | | | When a .gitignore specifies some folder "foo/", ensure that a file with the same name "foo" is not ignored.
| * attr: regression tests for ignore matchingEdward Thomson2015-05-121-0/+32
| | | | | | | | | | | | Ensure that when examining a .gitignore in a subdirectory, we do not erroneously apply the paths contained therein to the root of the repository. (Fixed in c02a0e4).
* | Merge pull request #3103 from libgit2/cmn/local-push-messageEdward Thomson2015-05-131-2/+2
|\ \ | | | | | | Use the packbuilder in local push
| * | tests: don't push to our resourcescmn/local-push-messageCarlos Martín Nieto2015-05-131-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | A couple of tests use the wrong remote to push to. We did not notice up to now because the local push would copy individual objects, and those already existed, so it became a no-op. Once we made local push create the packfile, it became noticeable that there was a new packfile where it didn't belong.
* | | Fix a few leaksCarlos Martín Nieto2015-05-132-0/+3
| | | | | | | | | | | | | | | The interesting one is the notification macro, which was returning directly on a soft-abort instead of going through the cleanup.
* | | Merge pull request #3115 from libgit2/cmn/clone-submoduleEdward Thomson2015-05-131-0/+55
|\ \ \ | |/ / |/| | submodule: add test initialising and cloning a repo
| * | submodule: add test initialising and cloning a repocmn/clone-submoduleCarlos Martín Nieto2015-05-121-0/+55
| |/ | | | | | | | | | | | | | | We have a few tests checking each step, but we do not yet have a test which tests the documented workflow for creating a submodule, namely `setup_add` followed by cloning into it, followed by `add_finalize`. Add such a test to protect against regressions in this workflow.
* | remote: remove git_remote_save()Carlos Martín Nieto2015-05-131-12/+0
| | | | | | | | | | 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-136-84/+25
| | | | | | | | | | | | | | | | | | | | | | | | 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-134-24/+20
| | | | | | | | | | 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-132-4/+4
| | | | | | | | | | | | 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-134-12/+12
| | | | | | | | | | | | | | 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: remove url and pushurl from the save logicCarlos Martín Nieto2015-05-133-12/+20
| | | | | | | | | | | | 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-1313-204/+140
|/ | | | | | | | | | | | | | 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.
* stash_apply: provide progress callbacksEdward Thomson2015-05-111-0/+45
|
* stash_apply: provide its own options structureEdward Thomson2015-05-112-17/+43
|
* stash: test checkout notify callbacksEdward Thomson2015-05-111-0/+52
|
* stash: return GIT_EMERGECONFLICT on merge conflictEdward Thomson2015-05-111-1/+1
|
* stash: refactor to use merge_iteratorsEdward Thomson2015-05-111-12/+12
|
* stash apply: check out a tree, not piecewiseEdward Thomson2015-05-111-2/+2
|
* index: introduce git_index_read_indexEdward Thomson2015-05-111-0/+73
|
* merge: merge iteratorsEdward Thomson2015-05-111-1/+13
|
* Added git_stash_apply() and git_stash_pop() APIsPierre-Olivier Latour2015-05-111-0/+215
|
* Merge pull request #3079 from ethomson/configCarlos Martín Nieto2015-05-041-0/+202
|\ | | | | Configuration changes for handling multiple of the same sections
| * config: test all multivars are updatedEdward Thomson2015-05-041-6/+16
| | | | | | | | | | | | If a multivar exists within two sections (of the same name) then they should both be updated in a `set_multivar`. Ensure that this is the case.
| * config: use wildcard in test instead of empty exprEdward Thomson2015-05-041-1/+1
| |
| * config: cleanup some now-unused variablesEdward Thomson2015-05-041-2/+0
| |
| * Test setting config var under duplicate header.Ryan Roden-Corrent2015-05-041-0/+49
| | | | | | | | | | | | | | | | | | | | Add a test that exposes a bug in config_write. It is valid to have multiple separate headers for the same config section, but config_write will exit after finding the first matching section in certain situations. This test proves that config_write will duplicate a variable that already exists instead of overwriting it if the variable is defined under a duplicate section header.
| * config: examine whole file when writingEdward Thomson2015-05-041-0/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously we would try to be clever when writing the configuration file and try to stop parsing (and simply copy the rest of the old file) when we either found the value we were trying to write, or when we left the section that value was in, the assumption being that there was no more work to do. Regrettably, you can have another section with the same name later in the file, and we must cope with that gracefully, thus we read the whole file in order to write a new file. Now, writing a file looks even more than reading. Pull the config parsing out into its own function that can be used by both reading and writing the configuration.
| * config: test overwriting cvar in multiple regionsEdward Thomson2015-05-041-0/+36
| |
| * config: ensure we can write to an empty fileEdward Thomson2015-05-041-0/+72
| |
* | checkout test: better case-insensitive test on MacEdward Thomson2015-05-041-3/+29
| | | | | | | | | | | | | | | | On Mac OS, `realpath` is deficient in determining the actual filename on-disk as it will simply provide the string you gave it if that file exists, instead of returning the filename as it exists. Instead we must read the directory entries for the parent directory to get the canonical filename.
* | status test: always test the new file pathEdward Thomson2015-05-041-8/+12
| |
* | checkout test: only run icase on icase platformEdward Thomson2015-05-042-79/+61
| |
* | checkout: remove blocking dir when FORCEdEdward Thomson2015-05-041-7/+91
| |
* | Revert "Always checkout with case sensitive iterator"Edward Thomson2015-05-041-2/+13
| | | | | | | | This reverts commit 40d791545abfb3cb71553a27dc64129e1a9bec28.
* | checkout test: ensure we write to casechanged dirEdward Thomson2015-05-041-0/+57
| | | | | | | | | | | | Ensure that on a case insensitive filesystem that we can checkout into some folder 'FOLDER' that exists on disk, even if the target of the checkout is a different case (eg 'folder').
* | checkout test: ignore unstaged case-changing renamesEdward Thomson2015-05-041-0/+22
|/ | | | | | | | On Windows, you might sloppily rewrite a file (or have a sloppy text editor that does it for you) and accidentally change its case. (eg, "README" -> "readme"). Git ignores this accidental case changing rename during checkout and will happily write the new content to the file despite the name change. We should, too.
* Merge pull request #3087 from ethomson/pr/3054Carlos Martín Nieto2015-05-043-13/+54
|\ | | | | Performance Improvements to Status on Windows
| * git_path_diriter: next shouldn't take path ptrEdward Thomson2015-05-011-9/+50
| | | | | | | | | | | | | | | | The _next method shouldn't take a path pointer (and a path_len pointer) as 100% of current users use the full path and ignore the filename. Plus let's add some docs and a unit test.
| * git_path_dirload: use git_path_diriterEdward Thomson2015-05-011-1/+1
| |
| * Improvements to ignore performance on Windows.J Wyman2015-04-281-3/+3
| | | | | | | | Minimizing the number directory and file opens, minimizes the amount of IO thus reducing the overall cost of performing ignore operations.
* | Merge pull request #3059 from libgit2/cmn/negotiation-notifyEdward Thomson2015-05-011-1/+1
|\ \ | | | | | | [WIP/RFC] push: report the update plan to the caller
| * | push: report the update plan to the callercmn/negotiation-notifyCarlos Martín Nieto2015-04-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
View Lorry Controller Status