| Age | Commit message (Collapse) | Author |
|
|
|
Git utilizes multiple environment variables to control various
behaviours. Make sure to set LC_MESSAGES on a copy of the environment
instead of discarding any variables that may be set by the user or
default shell environment such as EDITOR.
Add test to assert that when overriding GIT_EDITOR via os.environ that
the modified value will be picked up by and git commands called.
|
|
boppreh-patch-1
Adjusted patch to only run git command in shell mode on windows.
Conflicts:
git/cmd.py
|
|
|
|
|
|
Fixed most pressing issues, more to come in next commit as we introduced
a regression here.
Conflicts:
git/objects/commit.py
git/refs/log.py
git/refs/symbolic.py
|
|
Remove Byte Order Mark from git/cmd.py
|
|
The Unicode Byte Order Mark is usually unwanted. git/cmd.py had one
inserted in 2008 by cf37099e, a commit that fix a Windows related issue
which indicate the file has most probably be edited with a text editor
that automatically insert the Byte Order Mark.
Remove the BOM from git/cmd.py
For details aboute the BOM:
https://en.wikipedia.org/wiki/Byte_order_mark
|
|
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
|
|
johnsca-sf-master
Conflicts:
git/cmd.py
git/objects/commit.py
git/objects/fun.py
git/objects/util.py
git/remote.py
git/repo/base.py
git/test/lib/helper.py
git/test/test_commit.py
git/test/test_fun.py
git/util.py
|
|
The lines were added in commit b38020ae , and I might consider a patch release soon
or get ready with 0.3.3. Lets hope not too many installations will be affected.
|
|
Changed motivated by https://github.com/gitpython-developers/GitPython/pull/52
|
|
syabro-patch-1
Note by Sebastian Thiel: Was already fixed
Conflicts:
git/refs/reference.py
|
|
GPG signature support on commit object.
|
|
It represents the latest state on github, which should be better than
what's installed by default.
[skip ci]
|
|
|
|
Merged fd leaks fix from the master to the 0.3 version
|
|
Ensure consistent output from git command
|
|
Fix issue #41: repo.is_dirty() on empty repository with stashed files
|
|
Fix the `git version` parser.
|
|
GitRunCommand exception can store stdout output too.
|
|
0.3 with unicode fixes
|
|
Signed-off-by: David Black <dblack@atlassian.com>
|
|
(cherry picked from commit ca2b901e7229fc5c793762fd4e4c1c38c5a78e80)
|
|
(cherry picked from commit 8fa25b1cd5a82679c7b12d546b96c30cafed0559)
Signed-off-by: David Black <dblack@atlassian.com>
Conflicts:
git/test/test_git.py
|
|
Some git commands, like git merge outputs their problems onto stdout,
instead of stderr, which will be thrown away by the current setup. This
change allows the GitPython commands to store the stdout's value too,
in case of error.
|
|
|
|
|
|
Originals:
Pull request "GPG signature support on commit object" #124 by Tatsuki Sugiura.
https://github.com/gitpython-developers/GitPython/pull/124
commit 8065d2abdbb18e09560fc061807301b4c834d5a7
commit 62ecd6c66a84144632b045696326af503ee8cd4e
|
|
The git command output can vary by language which would cause assertions
errors when parsing the output.
On POSIX system the language used by git can be adjusted by LC_MESSAGES.
The special language 'C' is guaranteed to be always available and is
whatever default the software has been written in (usually english, the
case for git).
Thus passing LC_MESSAGES to Popen will ensure we receive from git a
consistent output regardless of the user preference.
Addresses #153
|
|
See https://github.com/gitpython-developers/GitPython/issues/172 for
more information
|
|
Git supports fetching many refs at once - support this in GitPython
too for more efficient operations when selectively mirroring
repositories.
|
|
https://github.com/gitpython-developers/GitPython/commit/f362d10fa24395c21b1629923ccd705ba73ae996
Related to #43
|
|
|
|
|
|
|
|
|
|
|
|
|
|
type in python.
The latter will break code that assumes it will get a string.
|
|
Fixes creating a Repo for a submodule (#155)
|
|
Add __call__ method to Git object to allow
passing git command options to the executable
requires flag to transform_kwargs
add unit tests
Change-Id: If1bc01008e66d3fd3811c15b56e58f38c95b9887
|
|
Add __call__ method to Git object to allow
passing git command options to the executable
requires flag to transform_kwargs
add unit test
Change-Id: If1bc01008e66d3fd3811c15b56e58f38c95b9887
|
|
Fixes #155.
|
|
Add __call__ method to Git object to allow
passing git command options to the executable
Change-Id: If1bc01008e66d3fd3811c15b56e58f38c95b9887
|
|
|