| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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
|
|
Renamed context manager 'with_environment' to 'custom_environment'.
On my way to implement sshkey test.
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
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
|
|
The latter happened as now BadName is thrown, instead of BadObject.
Changes.rst was marked accordingly
|
|
Fixes #50
|
|
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).
|
|
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.
|
|
There have been rather obvious errors in there, as we forgot to unregister
the filehandles. Now we will read from a buffer ourselves, which should be
faster and ideally, doesn't lead to spurious errors anymore.
Related to #232
|
|
This simplification should improve performance and remove issues like those
in #232.
NOTE: Debug code is still contained here
|
|
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
|
|
Fixes #235
[ci skip]
|
|
Assured unicode values are supported when reading the configuration,
and when getting author/committer information from the environment.
Fixes #237
|
|
Once again, __del__ is not being called as usual anymore in python 3 ... .
|
|
path
Fixes #238
|
|
A test verifies it's truly working.
Related to #238
|
|
Improved a test to assure multiple update(init=False|True) calls don't
throw.
Fixes #93
|
|
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
|
|
This also means that now we seem to be able to properly handle .git files in submodules
Related to #233
|
|
The root-submodule test is still failing though, this time even earlier
than before
|
|
A simple test verifies this at least.
|
|
However, a simple test-case still fails for reasons not yet understood.
There is more to be fixed here - .remove() still fails.
|
|
There is some more work to do, as renames and updates still have to be
adjusted accordinlgy.
Relates #233
|
|
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]
|
|
It actually revealed a bug in the implementation of Submodule.add,
which just showed in python 3 for the wrong reasons. Thankfully,
failing tests after all allowed to get this issue fixed ... .
|
