| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
In c96476b, the new default_name nested function does not contain a
retun statement. This leads to an issue when the environment variables
are not present, where the actor name would not be set.
Signed-off-by: Athos Ribeiro <athos@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Calling getpass.getuser may lead to breakage in environments where there
is no entries in the /etc/passwd file for the current user.
Setting the environment variables for the git user configurations should
prevents GitPython from using values from /etc/passwd. However, doing so
will not prevent reading /etc/passwd and looking for an entry with the
current user UID.
This patch changes the behavior described above so GitPython will
perform a lazy evaluation of /etc/passwd, only doing so when the
environment variables for the git user configuration are not available.
Signed-off-by: Athos Ribeiro <athos@redhat.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's possible to specify a pathspec (eg :!foo) to git diff/status/...
but it currently fails with:
git.exc.GitCommandError: Cmd('/usr/bin/git') failed due to: exit code(128)
cmdline: /usr/bin/git diff --abbrev=40 --full-index --raw :!foo
stderr: 'fatal: ambiguous argument ':!foo': unknown revision or path not in the working tree.
Add missing '--' to the arguments to fix this ambiguity
Signed-off-by: Arnaud Patard <apatard@hupstream.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
There's no easy way to re-create a commit (i.e. for rewriting purposes), because dates must be formatted as strings, passed, then parsed back.
This patch allows parse_date() to accept datetime instances, such as those produced by from_timestamp() above.
|
|
|
|
|
|
|
|
|
| |
which installs the current codebase in a venv
and runs 'import git' to test if codebase can be
installed properly.
This adds virtualenv to the test requirements
Signed-off-by: Konrad Weihmann <kweihmann@outlook.com>
|
|
|
|
|
|
|
|
|
| |
This should ensure that tests are NOT packaged into
release package by setuptools, as tests are development
only
+ fixtures after moving
Signed-off-by: Konrad Weihmann <kweihmann@outlook.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
This should ensure that tests are NOT packaged into
release package by setuptools, as tests are development
only
+ fixtures after moving
Signed-off-by: Konrad Weihmann <kweihmann@outlook.com>
|
|
|
|
| |
adjusted
|
| |
|
|
|
|
| |
value, and is not using ORIG_HEAD anymore
|
| |
|
| |
|
|
|
|
| |
entries, including test
|
|
|
|
|
|
| |
message much better
Added test for deletion of reflog file when the corresponding ref is deleted
|
|
|
|
| |
gets written
|
| |
|
|
|
|
| |
much easier. There is some bug in it though, it still needs fixing
|
|
|
|
| |
support which cannot be exposed using the respective property. Ref-Creation is now fully implemented in python. For details, see doc/source/changes.rst
|
| |
|
|
|
|
|
|
| |
actually write_append the new entry, instead of rewriting the whole file. Added file-locking and directory handling, so the implementation should be similar (enough) to the git reference implementation.
Next up is to implement a way to update the reflog when changing references, which is going to be a little more complicated
|
|
|
|
| |
set during merge and rebase, and probably everything that changes the ref more drastically. Probably I have to reread that. What needs to be adjusted though is the reflog
|
|
|
|
|
|
| |
accordingly. Added methods to Actor to retrieve the global committer and author information
Reflog: implemented and tested append_entry method
|
|
|
|
| |
supported, mainly because I don't need it
|
| |
|
| |
|
|
|
|
|
|
| |
TestCase scetched out for now
tests: Added tests to verify that objects don't have a dict. Previously, due to a missing __slots__ member in Serializable, most objects would indeed have a dict, although the opposite was intended
|
|
|
|
| |
tests to work with the new directory structure
|
| |
|
|
|
|
| |
incorrect repository
|
|
|
|
| |
directory
|
|
|
|
| |
fact, it didn't work, and ... something else keeps them open. Its odd, its weird, its windows, and I give up on it for now
|
| |
|
|
|
|
| |
was returned in the submodules super repository, not in the submodule's module
|
|
|
|
| |
run often enough, which is because they intentionally don't have a package initialization file
|
|
|
|
|
|
| |
submodule names. Also, a major bug was fixed that cased submodules to always being updated recursively when using the RootModule.update method
submodule: previously, it would update the repository configuration during add(), but in fact it must be done during update() when the module is cloned, which is how the git-submodule implementation works
|
| |
|
| |
|
|
|
|
| |
the restricted tests are concerned
|
|
|
|
| |
submodule removals, as well as url changes
|
|
|
|
| |
moved later if the configuration changed, and actually it also verifies that the url-change is handled correctly (as we changed the url from the default to the local path)
|
| |
|
|
|
|
|
|
| |
being a special case of the commit method; includes tests
util: Fixed iterable lists, which broke due to an incorrectly implemented __contains__ method
|