| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
subdirectory"
This reverts commit eb792ea76888970d486323df07105129abbbe466.
Seems to break CI
Related to #1000
|
|
|
|
|
|
|
|
|
| |
subdirectory
This will work for default git object databases only, which use git as
object database directly.
Related to #1000
|
| |
|
|
|
|
| |
dir, to eliminate path length errors on Windows
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes Repo("foo") work when foo/.git is a file of the form created
by "git worktree add", i.e. it's a text file that says:
gitdir: /home/me/project/.git/worktrees/bar
and where /home/me/project/.git/ is the nominal gitdir, but
/home/me/project/.git/worktrees/bar has this worktree's HEAD etc and a
"gitdir" file that contains the path of foo/.git .
Signed-off-by: Peter Jones <pjones@redhat.com>
|
|\ |
|
| |\
| | |
| | |
| | | |
ankostis-cygwin
|
| | | |
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
Conflicts:
git/repo/base.py
git/repo/fun.py
git/test/test_submodule.py
|
| |/
| |
| |
| |
| |
| |
| | |
+ Expansion of paths also `osp.normalize()` them.
+ Make Repo-fields --> class-fields to avoid initializations on
construct.
+ Explain and rename `git.repo.fun.find_git_dir()` is for submodules
(`find_submodule_git_dir()`).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
+ Decygpath sm's `.git` file contents.
+ Polish another path in `git add`; actually no main-code changes, just
a replace \-->/ on a relative(!) path to make cygwin-git to work.
- REGRESSION `test_git_submodules_and_add_sm_with_new_commit` asks for
user/email settings.
- Cygwin TCs failing:
- PY2: err: 2, fail: 1
- PY3: err: 2, fail: 1
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
| |
+ Mark all unused vars and other non-pep8 (PyDev) warnings
+ test_utils:
+ enable & fix forgotten IterableList looped path.
+ unittestize all assertions.
+ remote: minor fix progress dispatching unknown err-lines
|
|
|
|
|
|
| |
+ Modify lock/read-config-file code to ensure files closed.
+ Use `with GitConfigarser()` more systematically in TCs.
+ Clear any locks left hanging from prev Tcs.
+ Util: mark lock-files as SHORT_LIVED; save some SSDs...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As GitPython is in maintenance mode, there will be no new features.
However, I believe it's good idea to explicitly state we do not support
certain things if this is the case.
Therefore, when worktrees are encountered, we will throw an specific
exception to indicate that.
The current implementation is hacky to speed up development,
and increases the risk of failing due to false-positive worktree
directories.
Related to #344
|
| |
|
|
|
|
|
|
| |
That way they are protected from regression.
Fixes #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.
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
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
|
| |
| |
| |
| |
| |
| | |
E301 expected 1 blank line, found 0
E302 expected 2 blank lines, found 1
E303 too many blank lines (n)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
W191 indentation contains tabs
E221 multiple spaces before operator
E222 multiple spaces after operator
E225 missing whitespace around operator
E271 multiple spaces after keyword
W292 no newline at end of file
W293 blank line contains whitespace
W391 blank line at end of file
|
| |
| |
| |
| | |
Fixes #155.
|
|/
|
|
| |
probably a good idea to go a little more pep8 (and fix sins of my youth ;) )
|
|
|
|
| |
looked like hexshas. Thanks to Ning (frostyplanet) who pointed this issue out
|
|
adjusted
|