summaryrefslogtreecommitdiff
path: root/git/test
Commit message (Collapse)AuthorAgeFilesLines
* fix(config): selective cfg write;fix cfg parserSebastian Thiel2015-04-222-6/+12
| | | | | | | | | | | * config parser now handles quoted values correctly. This doesn't hamper multi-line support. * added regression test to travis to assure we will be warned if we rewrite and break the user's .gitconfig file * only rewrite configuration files if we actually called a mutating method on the writer. Previously it would always rewrite it. Fixes #285
* test: make git-daemon port configurable via envBenedikt Morbach2015-04-212-5/+10
| | | | | add a GIT_PYTHON_TEST_GIT_DAEMON_PORT to set a port other than 9418, for example for when you already have a daemon running on that port.
* test: Make git-daemon only listen on localhostBenedikt Morbach2015-04-211-1/+1
| | | | | | | | | | | | No reason to expose a daemon to all interfaces when it is only used for tests, which connect to localhost anyway. I'd love to use localhost here instead, but the git-daemon man page points out: If IPv6 is not supported, then --listen=hostname is also not supported and --listen must be given an IPv4 address. I don't know of a way to check if git has ipv6 support, but 127.0.0.1 should be around for the foreseeable future
* fix(test_docs): we are at major version 1 nowSebastian Thiel2015-04-161-1/+1
| | | | It expected to see major version 0 though.
* Merge branch 'teeberg-master'Sebastian Thiel2015-04-081-9/+0
|\
| * Replace GIT_SSH with GIT_SSH_COMMAND for SSH key management.Jonas Trappenberg2015-02-091-9/+0
| | | | | | | | | | | | Also move untestable documentation out of test. Related: #234, #242
* | fix(test_cmd): handle GitCommandNotFound in testSebastian Thiel2015-04-081-5/+2
| | | | | | | | Related to #248
* | fix(remote): allow to raise during push/fetchSebastian Thiel2015-04-081-2/+1
| | | | | | | | | | | | | | | | | | | | Do not swallow non-zero exit status during push and fetch unless we managed to parse head information. This behaviour will effetively handle cases were no work was done due to invalid refspecs or insufficient permissions. Fixes #271
* | fix(docs): be clear about exit code handlingSebastian Thiel2015-04-081-3/+11
| | | | | | | | | | | | | | | | When pushing/pulling, we ignore errors unless it's exit code 128. The reason for this is now made explicit to make clear that issues are handled by PushInfo flags accordingly. Related #271
* | fix(index): don't write extension data by defaultSebastian Thiel2015-04-081-15/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It turned out that the index is not actually corrupted, which is good news. What happens is that `git` writes `TREE` extension data into the index, which causes it to write out the given tree *as is* next time a `git commit` is executed. When using `git add`, this extension data is maintained automatically. However, GitPython doesn't do that ... . Usually this is no problem at all, as you are supposed to use `IndexFile.commit(...)` along with `IndexFile.add(...)`. Thanks to a shortcoming in the GitPython API, the index was automatically written out whenever files have been added, without providing control over whether or not *extension data* will be written along with it. My fix consists of an additional flag in `IndexFile.add(...)`, which causes extension data not to be written by default, so commits can be safely done via `git commit` or `IndexFile.commit(...)`. However, this might introduce new subtle bugs in case someone is relying on extension data to be written. As this can be controlled through the said flag though, a fix is easily done in that case. Fixes #265
* | test(index): test for #265Sebastian Thiel2015-04-071-0/+15
| | | | | | | | | | However, it doesn't reproduce on the latest version of GitPython. Maybe it's on an older one.
* | fix(iter-commit): ambiguous argument errorSebastian Thiel2015-03-021-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In repositories like > git branch -a * test > ls test `repo.iter_commits` failed due to an ambigous argument (`'git rev-list test`). Now this cannot happen anymore. fixes #264
* | Added 'insert_kwargs_after' flag for consumption by _call_process.Sebastian Thiel2015-02-212-0/+7
|/ | | | | | While at it, all other invocations of .git in remote.py were reviewed Fixes #262
* Minor Flake8 fixes.Sebastian Thiel2015-02-092-5/+7
| | | | Latest version of it is required to show the issues travis shows as well
* BF: skip unicode filename test in env not supporting unicode encodingsYaroslav Halchenko2015-02-071-0/+9
|
* ENH: respect GIT_PYTHON_TEST_GIT_REPO_BASE env var in testsYaroslav Halchenko2015-02-071-1/+1
|
* This should fix the test failure on travisSebastian Thiel2015-01-301-0/+5
|
* Added test to verify we can handle fetch prunes.Sebastian Thiel2015-01-301-0/+13
| | | | | | They are just skipped. Fixes #249
* Removed Git.sshkey() as it couldn't be distributed properly.0.3.6Sebastian Thiel2015-01-222-17/+11
| | | | | | | However, I kept information on how to achieve the same thing with `custom_environment()` in the test. Related to #234
* Bumped version to 0.3.6Sebastian Thiel2015-01-221-6/+1
| | | | | | Unfortunately, installation of a executable script has proven to be so difficult thanks setuptools gloriousness, which will force me to remove that feature
* Improved performance of rev-parse test.Sebastian Thiel2015-01-221-2/+9
| | | | | | Hoping to make this significantly faster on travis. Related to #245
* Minor improvements to submodule test for windows portabilitySebastian Thiel2015-01-221-4/+4
| | | | | | | | | However, most tests fail for reasons unknown - SHA cannot be found. For now, I will wait until someone complains, as I doubt too many people will use it on windows. Related to #244
* Added test for `sshkey` context manager.Sebastian Thiel2015-01-222-5/+20
| | | | | | | | It verifies that the script is actually called. Interestingly, the shell script version works within an msysgit environment on windows. Fixes #234
* Merge branch 'master' into teeberg-masterSebastian Thiel2015-01-226-13/+340
|\ | | | | | | | | | | Need latest master to proceed with test Conflicts: doc/source/tutorial.rst
| * This should finally fix travis ciSebastian Thiel2015-01-221-1/+1
| |
| * Fetch now deals with custom refspecs much better.Sebastian Thiel2015-01-224-2/+28
| | | | | | | | | | | | | | | | | | Even though the test-csae only verifies this spec: +refs/pull/*:refs/heads/pull/* I could locally verify that it indeed handles other ones just as well: +refs/pull/*:refs/pull/* Fixes #243
| * Overhauled all tutorials, and placed them in a unit-test.Sebastian Thiel2015-01-223-12/+304
| | | | | | | | | | | | That way they are protected from regression. Fixes #239
* | Intermediate commit on my way to get this finalized.Sebastian Thiel2015-01-221-12/+28
| | | | | | | | | | Renamed context manager 'with_environment' to 'custom_environment'. On my way to implement sshkey test.
* | Add a few testsJonas Trappenberg2015-01-211-0/+20
| |
* | Fix some typosJonas Trappenberg2015-01-211-2/+2
|/
* Fixed regression in test-suite for IndexFileSebastian Thiel2015-01-211-4/+8
| | | | | Previously, it checked for AssertionErrors, now we have to implement need-unbare-repo check ourselves.
* Added advance usage examples to tutorial and made minor fixes.Sebastian Thiel2015-01-214-12/+144
| | | | | | GIT_PYTHON_TRACE would actually fail (now) if we debugged archive operations. Related to #239
* Initial set of documentation improvements, and a fix to the submodule tests.Sebastian Thiel2015-01-212-5/+46
| | | | | | Now travisci tests should work once again. Related to #239
* Merge branch 'issue-232-reproduction' - keep fetch/pull simplificationsSebastian Thiel2015-01-211-0/+1
|\ | | | | | | | | | | Make sure we keep the improvements made to fetch and pull Relates to #232
| * Remote.fetch|pull() will not use poll/threads anymore as only stderr is read.Sebastian Thiel2015-01-201-0/+1
| | | | | | | | | | | | | | This simplification should improve performance and remove issues like those in #232. NOTE: Debug code is still contained here
* | Assured that branch changes are properly handled.Sebastian Thiel2015-01-211-2/+65
| | | | | | | | | | | | | | | | | | Previously we could try to remove the branch we are on. Of course, we have a test-case elaborate enough to verify we don't destroy changes in submodules accidentally. Therefore I am confident that this implementation is correct. Fixes #49
* | Fixed flake8 and a minor test regression.Sebastian Thiel2015-01-202-4/+4
| | | | | | | | | | The latter happened as now BadName is thrown, instead of BadObject. Changes.rst was marked accordingly
* | Impemented keep_going flag for `Submodule.update()`Sebastian Thiel2015-01-201-2/+5
| | | | | | | | Fixes #50
* | Submodule.parent_commit() now automatically points to repo.head unless it ↵Sebastian Thiel2015-01-201-6/+4
| | | | | | | | | | | | | | | | was set before. That way, you don't always have to keep the parent commit uptodate when changing the repo, which can lead to errors which are hard to debug and make no sense to the user, who previously never set parent_commit (yet it matters thanks to the cache).
* | Greatly improved possible safety of Submodule.update(), which is used by ↵Sebastian Thiel2015-01-201-30/+83
| | | | | | | | | | | | | | | | | | | | | | | | default. Previously, the implementation would gladly reset new commits in submodules, and/or reset a dirty working tree. Now the new force_reset/force flag has to be specified explicitly to get back to the old behaviour. All submodule tests except for one are working.
* | Added tutorial about initializing a repository.Sebastian Thiel2015-01-191-0/+26
| | | | | | | | | | | | | | | | Additionally, for this and future examples, there is a test_doc.py suite to contain all code mentioned in the docs. That way, we know if things stop working. Fixes #236
* | Improved unicode handling when using os.environ or GitConfigParserSebastian Thiel2015-01-191-1/+2
| | | | | | | | | | | | | | Assured unicode values are supported when reading the configuration, and when getting author/committer information from the environment. Fixes #237
* | Fixed configuration file test - release call was missing.Sebastian Thiel2015-01-191-0/+1
| | | | | | | | Once again, __del__ is not being called as usual anymore in python 3 ... .
* | Submodule.move() will auto-rename the submodule if the name was equal to the ↵Sebastian Thiel2015-01-191-1/+4
| | | | | | | | | | | | path Fixes #238
* | Implemented Submodule.rename()Sebastian Thiel2015-01-193-0/+38
| | | | | | | | | | | | A test verifies it's truly working. Related to #238
* | Submodule.move() fixed to deal with 'non-gitfile' clones appropriately.Sebastian Thiel2015-01-191-4/+14
| | | | | | | | | | | | | | Improved a test to assure multiple update(init=False|True) calls don't throw. Fixes #93
* | Basic submodule tests are working once again !Sebastian Thiel2015-01-191-11/+15
| | | | | | | | | | | | | | | | After all, it was easier than expected. It seems that previous assertions the test made should have never been true to begin with. Thus we might have improved the test thanks to our improved implementation. Fixes #233
* | Submodule.remove() now seems to work properly, nearly all tests are back.Sebastian Thiel2015-01-171-4/+13
| | | | | | | | | | | | This also means that now we seem to be able to properly handle .git files in submodules Related to #233
* | Made sure dry-run is properly implemented in Submodule.remove()Sebastian Thiel2015-01-171-4/+7
| | | | | | | | | | The root-submodule test is still failing though, this time even earlier than before
* | Submodule.remove() now deals with .git files correctly.Sebastian Thiel2015-01-171-4/+6
| | | | | | | | A simple test verifies this at least.
View Lorry Controller Status