| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| | |
Related to #224
[ci skip]
|
| |
| |
| |
| |
| | |
Think about how expensive this single invisible character was, with
all the time and energy spent on it !
|
| |
| |
| |
| | |
Fixes #260
|
| |
| |
| |
| |
| |
| | |
While at it, all other invocations of .git in remote.py were reviewed
Fixes #262
|
|\ \
| | |
| | | |
BF: do not checkout master -- that ruins testing of PRs
|
|/ /
| |
| |
| | |
original HEAD
|
| | |
|
| |
| |
| |
| |
| | |
... as we are now running out of file handles.
Previously, it worked ... and gitpython didn't change
|
| |
| |
| |
| |
| |
| |
| | |
As I am pretty sure to have tested it with 1.7.0, I assume they
added the git file feature somewhere between .0 .10.
Fixes #252
|
| |
| |
| |
| | |
Related to #252
|
| |
| |
| |
| | |
It's new in the latest version of flake - thanks travis for letting me know.
|
|/
|
|
|
|
| |
That, over time, could have caused slow downs due to file-system hassle.
Fixes #258
|
|
|
|
| |
Related to #255
|
|\ |
|
| |\
|/ /
| |
| | |
https://github.com/yarikoptic/GitPython into yarikoptic-bf/run_hooks_from_working_dir
|
| |
| |
| |
| |
| |
| |
| |
| | |
Otherwise commit hook might rightfully fail, as happens if
repository is e.g. git-annex repository. See e.g. now failing
https://travis-ci.org/datalad/datalad/builds/49802394\#L1590
which seems to pass tests nicely with patch as this
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
Latest version of it is required to show the issues travis shows as well
|
| | |
|
|/ |
|
|
|
|
| |
Fixes #246
|
|
|
|
|
|
| |
Currently, people put it onto the mailing list and on stack overflow
[ci skip]
|
| |
|
|
|
|
|
|
| |
They are just skipped.
Fixes #249
|
|
|
|
| |
Fixes #250
|
|
|
|
|
|
|
| |
However, I kept information on how to achieve the same thing with
`custom_environment()` in the test.
Related to #234
|
|
|
|
|
|
| |
Unfortunately, installation of a executable script has proven to be so
difficult thanks setuptools gloriousness, which will force me to remove
that feature
|
|
|
|
|
|
| |
Hoping to make this significantly faster on travis.
Related to #245
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
It verifies that the script is actually called.
Interestingly, the shell script version works within an msysgit environment
on windows.
Fixes #234
|
|\
| |
| |
| |
| |
| | |
Need latest master to proceed with test
Conflicts:
doc/source/tutorial.rst
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| | |
That way they are protected from regression.
Fixes #239
|
| |
| |
| |
| |
| | |
Renamed context manager 'with_environment' to 'custom_environment'.
On my way to implement sshkey test.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
| |
Previously, it checked for AssertionErrors, now we have to implement
need-unbare-repo check ourselves.
|
|
|
|
|
|
| |
GIT_PYTHON_TRACE would actually fail (now) if we debugged archive operations.
Related to #239
|
|
|
|
|
|
| |
Now travisci tests should work once again.
Related to #239
|
|\
| |
| |
| |
| |
| | |
Make sure we keep the improvements made to fetch and pull
Relates to #232
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This simplification should improve performance and remove issues like those
in #232.
NOTE: Debug code is still contained here
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
FETCH_HEAD.
This data will be written into the git-repository itself, prefixed with the
number of the operation.
Thus, a test-run with exactly one fetch operation would look like this afterwards:
ls -l .git
total 96
-----> -rw-r--r-- 1 byron staff 141B Jan 16 11:54 000_debug_git-python_FETCH_HEAD <-----
-----> -rw-r--r-- 1 byron staff 180B Jan 16 11:54 000_debug_git-python_stderr <-----
-rw-r--r-- 1 byron staff 487B Jan 16 11:54 FETCH_HEAD
-rw-r--r-- 1 byron staff 22B Jan 16 11:54 HEAD
-rw-r--r-- 1 byron staff 41B Jan 16 11:54 ORIG_HEAD
drwxr-xr-x 2 byron staff 68B Jan 16 11:54 branches/
-rw-r--r-- 1 byron staff 560B Jan 16 11:54 config
-rw-r--r-- 1 byron staff 73B Jan 16 11:54 description
drwxr-xr-x 11 byron staff 374B Jan 16 11:54 hooks/
-rw-r--r-- 1 byron staff 13K Jan 16 11:54 index
drwxr-xr-x 3 byron staff 102B Jan 16 11:54 info/
drwxr-xr-x 4 byron staff 136B Jan 16 11:54 logs/
drwxr-xr-x 12 byron staff 408B Jan 16 11:54 objects/
-rw-r--r-- 1 byron staff 1.2K Jan 16 11:54 packed-refs
drwxr-xr-x 5 byron staff 170B Jan 16 11:54 refs/
[ci skip]
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|