| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
Adds the optional keyword parameter env to Repo.clone_from(). The parameter
is a dictionary containing the desired environment variables for the git
clone invocation. The environment is applied to the temporary Git instance
before calling Repo._clone().
|
| |
|
|\
| |
| | |
support passing odbt for using with Repo
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* renamed `consider_submodules` to `submodules` to be in line with the
existing parameters. Nowadays I would prefer the `consider_` prefix,
but can't change the existing API and thus stick to the current
naming scheme.
* reduced amount of code in one portion to make it more maintainable.
Related to #294
|
|/
|
|
|
|
| |
There are cases when might not consider a directory dirty when a submodule has
changes. Particular case was git-up stashing changes where submodules are
irrelevant.
|
|
|
|
| |
Related to #255
|
|
|
|
|
|
|
|
| |
It verifies that the script is actually called.
Interestingly, the shell script version works within an msysgit environment
on windows.
Fixes #234
|
|
|
|
|
|
| |
That way they are protected from regression.
Fixes #239
|
|
|
|
|
|
| |
GIT_PYTHON_TRACE would actually fail (now) if we debugged archive operations.
Related to #239
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Fixes #235
[ci skip]
|
|
|
|
|
|
| |
A test verifies it's truly working.
Related to #238
|
|
|
|
|
|
| |
This also means that now we seem to be able to properly handle .git files in submodules
Related to #233
|
|
|
|
| |
A simple test verifies this at least.
|
|
|
|
|
|
| |
Fixes #7
[ci skip]
|
|
|
|
|
|
|
| |
This allows sub-trees to be archived as well, and makes `.archive()`
feature complete.
Fixes #67
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We implement it as described in this article:
http://stackoverflow.com/questions/1557183/is-it-possible-to-include-a-file-in-your-gitconfig
Thus we handle
* cycles
* relative and absolute include paths
* write-backs in case of writable GitConfigParser instances
Fixes #201
|
|
|
|
| |
Fixes #169
|
|
|
|
|
|
|
|
|
| |
required afterall.
Turns out that the now removed `read_gitfile` functions applied os.path.realpath which caused
the issue described in #224.
Fixes #224
|
|
|
|
|
|
|
|
|
| |
index related work.
That way, we don't try to compare a real-path to a non-real one, which would make the implementation think
a file is not actually part of the repository.
Fixes #224
|
|
|
|
|
|
|
| |
For some reason, I didn't trust the existing one as it tests that code
more indirectly.
Related to #160
|
|
|
|
|
|
|
| |
The point is that XDG_CONFIG_HOME is meant to point at the '.config' directory,
whereas '.config' has to be added only if HOME is used instead.
Fixes #160
|
|
|
|
| |
Fixes #160
|
|
|
|
|
|
| |
general.
Fixes #83
|
|
|
|
|
|
|
|
| |
Now by default, we will not walk up the directory structure and possibly find
git directories that the user didn't intend to find.
If required, that kind of behaviour can be turned back on.
Fixes #65
|
|
|
|
| |
Fixes #74
|
|
|
|
|
|
|
|
|
| |
Previously, an unresolvable ref name like HEAD would end up as HEX and
was presented as BadObject error, even though that exception is for
invalid shas only.
Now BadName is thrown, which converts into a more useful error message.
Improves #105
|
|
|
|
|
|
|
|
| |
Apparently, thanks to an incorrect version check, PY3 ended up using
a git command object database by default. This is now fixed.
Additionally, the update_cache code was adjusted to check for method-existence,
as it's valid to use object databases which simply don't have a
caching mechanism (like the git command object database)
|
| |
|
|
|
|
| |
Fixes #48
|
|
|
|
|
|
|
|
| |
At least leakage is considerably reduced.
Additionally, a test-case was added which triggers failure if auto-disposal
of resources wouldn't work.
Fixes #60
|
|
|
|
| |
Next up is using threads
|
| |
|
|
|
|
|
|
|
| |
And I have to wonder why git-daemon serves under py2.7, but really
wants receive-pack to be allowed under 3.4. Maybe it's a repository
override which for some reason doesn't work in py3.4 ? Maybe because
the change is not flushed ?
|
| |
|
| |
|
|
|
|
|
|
| |
However, StringIO really is ByteIO in most cases, and py2.7 should
run but doesn't.
This should be made work first.
|
|
|
|
| |
More to come, especially when it's about strings
|
| |
|
|
|
|
|
| |
There is more work to do though, as many imports are still incorrect.
Also, there are still print statements
|
|
|
|
|
| |
Commandline was
autopep8 -j 8 --max-line-length 120 --in-place --recursive --exclude "*gitdb*,*async*" git/
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
niyaton-separate-git-dir
Conflicts:
git/repo/base.py
|
| | |
|
| |
| |
| |
| | |
W291 trailing whitespace
|
| |
| |
| |
| | |
E261 at least two spaces before inline comment
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
E201 whitespace after '('
E202 whitespace before ')'
E203 whitespace before ':'
E225 missing whitespace around operator
E226 missing whitespace around arithmetic operator
E227 missing whitespace around bitwise or shift operator
E228 missing whitespace around modulo operator
E231 missing whitespace after ','
E241 multiple spaces after ','
E251 unexpected spaces around keyword / parameter equals
|