summaryrefslogtreecommitdiff
path: root/git/objects/submodule/root.py
Commit message (Collapse)AuthorAgeFilesLines
* reformat according to 'black' configuration file.Sebastian Thiel2022-05-181-34/+10
|
* Run everything through 'black'Sebastian Thiel2022-05-181-58/+146
| | | | | That way people who use it won't be deterred, while it unifies style everywhere.
* Fix various typosluz paz2022-05-071-1/+1
| | | Found via `codespell -q 3 -S ./git/ext/gitdb,./test/fixtures/reflog_master,./test/fixtures/diff_mode_only,./test/fixtures/reflog_HEAD`
* update types submodule/root.pyDominic2021-07-311-3/+1
|
* Fix submodule.util.py typesYobmod2021-07-061-10/+24
|
* Rmv root.py typesYobmod2021-07-061-24/+10
|
* Add types to submodule.root.pyYobmod2021-07-051-8/+13
|
* Make bytesIO forwardrefYobmod2021-07-051-3/+12
|
* Replace deprecated Logger.warn with Logger.warningHarmon2020-02-161-1/+1
|
* Rewrite unnecessary dict/list/tuple calls as literalsHugo2018-03-181-2/+2
|
* chore(lint): flake8Sebastian Thiel2016-12-081-1/+1
| | | | | | | | Interestingly only shows in particular python versions on travis. Maybe some caching effect? Locally it is reproducible easily, with the latest flake8
* Added NullHandlers to all loggers to preven "No handler" messagesJames Nowell2015-06-251-0/+1
| | | | | | | | When the code is run without setting up loggers, the loggers have no handlers for the emitted messages. The logging module displays: `No handlers could be found for logger "git.cmd"` on the console. By adding a NullHandler (a no-op) the message disappears, and doesn't affect logging when other handlers are configured.
* Assured that branch changes are properly handled.Sebastian Thiel2015-01-211-15/+10
| | | | | | | | | 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
* Fixed flake8 and a minor test regression.Sebastian Thiel2015-01-201-5/+6
| | | | | The latter happened as now BadName is thrown, instead of BadObject. Changes.rst was marked accordingly
* Impemented keep_going flag for `Submodule.update()`Sebastian Thiel2015-01-201-204/+217
| | | | Fixes #50
* Greatly improved possible safety of Submodule.update(), which is used by ↵Sebastian Thiel2015-01-201-8/+14
| | | | | | | | | | | | 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.
* initial set of adjustments to make (most) imports work.Sebastian Thiel2015-01-041-2/+5
| | | | More to come, especially when it's about strings
* Replaced ordered dict with standard version; used logging moduleSebastian Thiel2015-01-041-3/+5
| | | | All performance tests still print to stderr, but do so in a py3 compatible way
* Bumped version, updated changelog, reduced code smellSebastian Thiel2015-01-041-3/+7
| | | | | There is more work to do though, as many imports are still incorrect. Also, there are still print statements
* Applied autopep8Sebastian Thiel2014-11-191-44/+53
| | | | | Commandline was autopep8 -j 8 --max-line-length 120 --in-place --recursive --exclude "*gitdb*,*async*" git/
* pep8 linting (trailing whitespace)Antoine Musso2014-11-161-30/+30
| | | | W291 trailing whitespace
* pep8 linting (whitespace before/after)Antoine Musso2014-11-161-19/+19
| | | | | | | | | | | | | 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
* pep8 linting (blank lines expectations)Antoine Musso2014-11-161-2/+3
| | | | | | E301 expected 1 blank line, found 0 E302 expected 2 blank lines, found 1 E303 too many blank lines (n)
* pep8 linting (whitespaces)Antoine Musso2014-11-161-37/+37
| | | | | | | | | | | 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
* tabs to 4 spaces - this won't make integrating the patches easier, but it's ↵Sebastian Thiel2014-02-091-293/+293
| | | | probably a good idea to go a little more pep8 (and fix sins of my youth ;) )
* Fixed bug, which was so obvious that I am wondering how none of the test ran ↵Sebastian Thiel2010-12-011-1/+1
| | | | into that, or at least triggered it
* Moved everything into the git subdirectory - some tests still need to be ↵Sebastian Thiel2010-11-251-0/+315
adjusted
View Lorry Controller Status