| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Use $GIT_DIR when set
|
|
|
|
[skip ci]
|
|
|
|
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.
|
|
They don't seem to work anymore.
[skip ci]
|
|
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
|
|
They do not get updated for some reason, generally the
site is not quite production ready it seems, or is by
now overwhelmed.
[skip ci]
|
|
|
|
|
|
This mentions the instructions of what was discussed in #489.
|
|
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
|
|
|
|
|
|
|
|
Commit without executing hooks, fixes #468
|
|
Fixes #478
|
|
|
|
|
|
|
|
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
|
|
Fix issue #470
|
|
|
|
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
|
|
|
|
|
|
Relates to #446
|
|
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.
|
|
The main point is that from now on, tests are required to add
new features. If the fix is minor enough, not having a test
is probably alright.
That distinction is not represented in the contribution guide
as more tests are better - people should prefer to have a test
whenever they contribute anything.
My motivation to finally do this is the sad realization that
I grow too unconfident about the quality of some contributions
without having tests that proof they are valid. It's not enough
to not break anything that exists, as the current test-suite is
certainly not perfect either.
|
