| Age | Commit message (Collapse) | Author |
|---|
|
+ Fixed the hangs at `test_git:TestGit.test_handle_process_output()`.
[travisci skip]
|
|
+ Del extra spaces, import os.path as osp
|
|
Thanks to @yarikoptic for catching this one !
|
|
It ain't pretty, but should do the job.
Related to #514
|
|
Relying on the destructor will not work, even though
the code used to rely on it.
Now we handle failures more explicitly. Far from perfect,
but a good start for a fix.
Fixes #514
|
|
by demanding a space after a word remote, and space is explicitly described as
a delimiter in man git-config:
To begin a subsection put its name in double quotes, separated by space from the section name,
otherwise e.g.
File "/usr/lib/python2.7/dist-packages/datalad/support/gitrepo.py", line 836, in get_remote_branches
for remote in self.repo.remotes:
File "/home/yoh/deb/gits/python-git/git/repo/base.py", line 271, in remotes
return Remote.list_items(self)
File "/home/yoh/deb/gits/python-git/git/util.py", line 745, in list_items
out_list.extend(cls.iter_items(repo, *args, **kwargs))
File "/home/yoh/deb/gits/python-git/git/remote.py", line 453, in iter_items
raise ValueError("Remote-Section has invalid format: %r" % section)
ValueError: Remote-Section has invalid format: u'remotes'
|
|
Fixes #508
|
|
It's not optimal, as we can now return one of two types
which are only compatible in the most basic ways.
However, it is better than before, I presume.
Fixes #510
|
|
It's entirely untested if this repo still does the right thing,
but I'd think it does.
Fixes #504
|
|
As TagObjects can point to other TagObjects, we need
to keep going in order to resolve the final commit.
Fixes #503
|
|
Update Remotes section
The Remotes section was missing some pretty important info.
|
|
Assure that gpgsig is not initialized with None
to allow the automatic deserialization to kick in.
Fixes #500
|
|
|
|
|
|
|
|
is_dirty supports path. Fixes #482.
|
|
|
|
|
|
|
|
- add a second line to commit messages with the "BAD MESSAGE" text
- read in the log and confirm that the seond line is not in the log file
|
|
|
|
|
|
This fixes a UI problem with using GitPython from a GUI python probgram.
Each repo that is opened creates a git cat-file processs and that provess will create
a console window with out this change.
|
|
|
|
Add missing newline when writing a symbolic ref.
|
|
That way, we do not have to figure the change type out by
examining the diff object.
It's implemented in a way that should yield more desireable results
as we keep the change-type that git is providing us with.
Fixes #493
|
|
|
|
|
|
That way, we will not only get the summary line
contained in the blame, but fetch the full message.
This is more costly than the previous implementation
allowed it to be, but being less surprising/correct
certainly is the preferred behaviour here.
Fixes #485
|
|
|
|
|
|
|
|
We will now populate the old_commit on demand, which will
allow us to keep going even if the given commit does not
exist locally.
Fixes #461
|
|
|
|
|
|
Store raw path bytes in Diff instances
|
|
|
|
Previously, the following fields on Diff instances were assumed to be
passed in as unicode strings:
- `a_path`
- `b_path`
- `rename_from`
- `rename_to`
However, since Git natively records paths as bytes, these may
potentially not have a valid unicode representation.
This patch changes the Diff instance to instead take the following
equivalent fields that should be raw bytes instead:
- `a_rawpath`
- `b_rawpath`
- `raw_rename_from`
- `raw_rename_to`
NOTE ON BACKWARD COMPATIBILITY:
The original `a_path`, `b_path`, etc. fields are still available as
properties (rather than slots). These properties now dynamically decode
the raw bytes into a unicode string (performing the potentially
destructive operation of replacing invalid unicode chars by "�"'s).
This means that all code using Diffs should remain backward compatible.
The only exception is when people would manually construct Diff
instances by calling the constructor directly, in which case they should
now pass in bytes rather than unicode strings.
See also the discussion on
https://github.com/gitpython-developers/GitPython/pull/467
|
|
|
|
|
|
It usually fails on branches, which doesn't help
assessing PRs.
|
|
Adding support for git remote set-url/get-url API to Remote
|
|
gitpython-developers/fix-dont-choke-on-invalid-unicode-paths
Don't choke on (legitimately) invalidly encoded Unicode paths
|
|
|
|
|
|
It must only have the first line of the
commit messages, not the while multiple line log.
|
|
I see no need in verifying the status code.
It's enough to just get the error.
|
|
Just went through all changes and adjusted them to the best of my
abilities. As there are no tests to claim otherwise, I believe
this is correct enough.
However, it becomes evident that it's no longer possible to just
make changes without backing them with a respective test.
|
|
https://github.com/barry-scott/GitPython into barry-scott-pr-cmd-raise-with-stderr-on-error
|
|
This issue must have rosen from `to_progress_instance()`
being inserted in a spot where `None` was a legit value.
Fixes #462
|
