| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
* milestone URL: http://goo.gl/HFaeZ4
|
|
|
|
|
|
| |
They didn't show up as code-block
Related to #256
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
It goes along with the new one advertising the GIT_SSH_COMMAND
environment variable.
Related to #256
|
| |
| |
| |
| |
| |
| | |
Also move untestable documentation out of test.
Related: #234, #242
|
| |
| |
| |
| | |
Related to #248
|
| |
| |
| |
| |
| |
| |
| | |
... if it is not found. Previously, especially on windows, this wasn't
explicit.
Fixes #248, affects #126
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| | |
This should prevent a resource warning given in py3
Fixes #263
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| | |
Previously it would always adjust your system path, which is bad
behaviour.
|
| |
| |
| |
| |
| | |
However, it doesn't reproduce on the latest version of GitPython.
Maybe it's on an older one.
|
| | |
|
|\ \
| | |
| | | |
Fix broken worktree path with submodules on Windows
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
On Windows, `repo.create_submodule(...)` failed because git didn't recognize
the worktree path set in `.git/modules/sub/config` (`fatal: bad config file
line 6 in ./config`). This commit makes `_write_git_file_and_module_config`
convert the worktree path to the linux format (forward slashes) which git
recognizes.
|
|\ \
| | |
| | | |
Fix typo
|
|/ / |
|
|\ \
| | |
| | | |
Store path attribute on Diff object
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
If a file in a commit contains no changes (for example, if only the
file mode is changed) there will be no blob attached. This is
usually where the filename is stored, so without it, the calling
context can not tell what file was changed. Instead, always
store a_path and b_path on the Diff object so that information
is available.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|