Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | can flake be tamed?black-fmt | Sebastian Thiel | 2022-05-18 | 3 | -1/+4 |
| | |||||
* | doesn't look like 'black' can be taught to be consistent across versions | Sebastian Thiel | 2022-05-18 | 1 | -5/+0 |
| | |||||
* | reformat according to 'black' configuration file. | Sebastian Thiel | 2022-05-18 | 56 | -1753/+577 |
| | |||||
* | See if black can be tought to produce consistent results | Sebastian Thiel | 2022-05-18 | 2 | -1/+5 |
| | |||||
* | Revert "don't attempt black checking as it binds us to ever changing black ↵ | Sebastian Thiel | 2022-05-18 | 1 | -0/+5 |
| | | | | | | versions" This reverts commit 0c9d067e847377657b2208012df020b0b8650b5f. | ||||
* | don't attempt black checking as it binds us to ever changing black versions | Sebastian Thiel | 2022-05-18 | 1 | -5/+0 |
| | | | | Maybe there is a way to pin this? | ||||
* | improve compatibility of flake8 with black | Sebastian Thiel | 2022-05-18 | 4 | -6/+12 |
| | |||||
* | Revert "Remove flake8 linting in favor of `black` formatting" | Sebastian Thiel | 2022-05-18 | 12 | -6/+59 |
| | | | | This reverts commit a7c5d887e943aa51f2270e517954c024a8c01500. | ||||
* | Remove flake8 linting in favor of `black` formatting | Sebastian Thiel | 2022-05-18 | 12 | -59/+6 |
| | | | | `flake8` seems to dislike the formatting of black. | ||||
* | Run everything through 'black' | Sebastian Thiel | 2022-05-18 | 65 | -3917/+6673 |
| | | | | | That way people who use it won't be deterred, while it unifies style everywhere. | ||||
* | Merge pull request #1438 from luzpaz/typos | Sebastian Thiel | 2022-05-08 | 23 | -33/+33 |
|\ | | | | | Fix various typos | ||||
| * | Fix various typos | luz paz | 2022-05-07 | 23 | -33/+33 |
|/ | | | Found via `codespell -q 3 -S ./git/ext/gitdb,./test/fixtures/reflog_master,./test/fixtures/diff_mode_only,./test/fixtures/reflog_HEAD` | ||||
* | Merge pull request #1437 from glennmatthews/issue-1284 | Sebastian Thiel | 2022-05-05 | 4 | -20/+46 |
|\ | | | | | Strip usernames from URLs as well as passwords | ||||
| * | Fix #1284: strip usernames from URLs as well as passwords | Glenn Matthews | 2022-05-04 | 4 | -20/+46 |
|/ | |||||
* | Merge pull request #1423 from toku-sa-n/strip_newline_option | Sebastian Thiel | 2022-04-07 | 3 | -3/+16 |
|\ | | | | | feat(cmd): add the `strip_newline` flag | ||||
| * | fix(docs): remove an unexpected blank line | Hiroki Tokunaga | 2022-04-07 | 1 | -1/+0 |
| | | |||||
| * | docs: escape with backticks | Hiroki Tokunaga | 2022-04-07 | 1 | -1/+1 |
| | | |||||
| * | chore: `s/strip_newline/&_in_stdout` | Hiroki Tokunaga | 2022-04-07 | 2 | -7/+7 |
| | | |||||
| * | chore: add me to AUTHORS | Hiroki Tokunaga | 2022-04-06 | 1 | -0/+1 |
| | | |||||
| * | feat(cmd): add the `strip_newline` flag | Hiroki Tokunaga | 2022-04-06 | 2 | -2/+15 |
|/ | | | | | | | | This commit adds the `strip_newline` flag to the `Git.execute` method. When this flag is set to `True`, it will trim the trailing `\n`. The default value is `True` for backward compatibility. Setting it to `False` is helpful for, e.g., the `git show` output, especially with the binary file, as the missing `\n` may invalidate the file. | ||||
* | Allow `repo.create_head`'s `commit` arg to be a `SymbolicReference` | David Robertson | 2022-04-02 | 1 | -1/+2 |
| | | | | This matches the signature from `Head.create`. | ||||
* | Fixed setting ref with non-ascii in path | Dmitry Kalinin | 2022-03-23 | 1 | -1/+1 |
| | |||||
* | fix typos | Jerry Jones | 2022-02-24 | 1 | -5/+5 |
| | |||||
* | fix iter_commits comment, more in line with iter_items | Houssam Kherraz | 2022-02-24 | 1 | -2/+2 |
| | |||||
* | Deprecate GPG signature docs; stop signing releases | Sebastian Thiel | 2022-02-21 | 2 | -2/+7 |
| | | | | Related to https://github.com/gitpython-developers/gitdb/issues/77 | ||||
* | fix changelog | Sebastian Thiel | 2022-02-20 | 1 | -9/+2 |
| | |||||
* | bump patch level3.1.27 | Sebastian Thiel | 2022-02-20 | 1 | -1/+1 |
| | |||||
* | update changelog | Sebastian Thiel | 2022-02-20 | 1 | -0/+9 |
| | |||||
* | Low risk ReDoS vuln | theworstcomrade | 2022-02-20 | 1 | -1/+1 |
| | | | | https://huntr.dev/bounties/8549d81f-dc45-4af7-9f2a-2d70752d8524/ | ||||
* | Create SECURITY.md | Sebastian Thiel | 2022-02-12 | 1 | -0/+16 |
| | |||||
* | Let index.commit refer to correct method for parameter information (#1407) | Sebastian Thiel | 2022-02-03 | 1 | -1/+1 |
| | |||||
* | set unassigned stdin to improve pyinstaller compatibility | smokephil | 2022-01-21 | 1 | -2/+3 |
| | | | | To create a window application with pyinstaller, all suprocess input and output streams must be assigned and must not be None. https://stackoverflow.com/a/51706087/7076612 | ||||
* | Use bash to open extensionless hooks on windows | David Briscoe | 2022-01-14 | 2 | -4/+20 |
| | | | | | | | | | | | | | | | Fix #971. Partly resolve #703. If the hook doesn't have a file extension, then Windows won't know how to run it and you'll get "[WinError 193] %1 is not a valid Win32 application". It's very likely that it's a shell script of some kind, so use bash.exe (commonly installed via Windows Subsystem for Linux). We don't want to run all hooks with bash because they could be .bat files. Update tests to get several hook ones working. More work necessary to get commit-msg hook working. The hook writes to the wrong file because it's not using forward slashes in the path: C:\Users\idbrii\AppData\Local\Temp\bare_test_commit_msg_hook_successy5fo00du\CUsersidbriiAppDataLocalTempbare_test_commit_msg_hook_successy5fo00duCOMMIT_EDITMSG | ||||
* | keep track of upcoming changes | Sebastian Thiel | 2022-01-12 | 1 | -0/+8 |
| | |||||
* | import unittest adds 0.250s to script launch time | wonder-mice | 2022-01-12 | 1 | -2/+2 |
| | | | This should not be imported at root level, since it adds a lot of initialization overhead without need. | ||||
* | import unittest adds 0.250s to script launch time | wonder-mice | 2022-01-12 | 1 | -1/+1 |
| | | | This should not be imported at root level, since it adds a lot of initialization overhead without need. | ||||
* | fix documentation | Sebastian Thiel | 2022-01-10 | 1 | -0/+1 |
| | |||||
* | bump patch level3.1.26 | Sebastian Thiel | 2022-01-10 | 2 | -2/+12 |
| | |||||
* | Assure index file descriptor is closed after reader (#1394) (#1395) | Sebastian Thiel | 2022-01-10 | 1 | -1/+4 |
| | | | | A regression that was introduced with d79d20d. | ||||
* | Fix doc string error in Objects.Commit | Takuya Kitazawa | 2022-01-10 | 1 | -2/+2 |
| | |||||
* | prep version bump3.1.25 | Sebastian Thiel | 2022-01-07 | 2 | -1/+7 |
| | |||||
* | Revert "Use NUL character to extract meta and path from git diff" | Sebastian Thiel | 2022-01-07 | 1 | -3/+3 |
| | | | | This reverts commit 01f09888208341876d1480bd22dc8f4107c100f1. | ||||
* | Use git interpret-trailers for trailers property | Ket3r | 2022-01-07 | 2 | -19/+28 |
| | | | | | | | The whitespace handling and trailer selection isn't very trivial or good documented. It therefore seemed easier and less error prone to just call git to parse the message for the trailers section and remove superfluos whitespaces. | ||||
* | Add trailer as commit property | Peter Kempter | 2022-01-07 | 1 | -1/+40 |
| | | | | | | | | With the command `git interpret-trailers` git provides a way to interact with trailer lines in the commit messages that look similar to RFC 822 e-mail headers (see: https://git-scm.com/docs/git-interpret-trailers). The new property returns those parsed trailer lines from the message as dictionary. | ||||
* | Add failing unit test | Peter Kempter | 2022-01-07 | 1 | -0/+46 |
| | |||||
* | Use NUL character to extract meta and path from git diff | NHanser | 2022-01-07 | 1 | -3/+3 |
| | | | Use NUL character instead of semicolon to extract meta and path. Avoid errors in during git diff when dealing with filenames containing semicolons | ||||
* | Ignore mypi errors | Sebastian Thiel | 2022-01-07 | 1 | -0/+3 |
| | | | | | With each patch level it may bring up new issues that cause CI failure for without being related to the actual change. | ||||
* | Avoid taking a lock for reading | Sebastian Thiel | 2022-01-07 | 2 | -15/+2 |
| | | | | | | | This isn't needed as git will replace this file atomicially, hence we always see a fully written file when reading. Only when writing we need to obtain a lock. | ||||
* | DOC: fix typo | yogabonito | 2021-12-01 | 1 | -2/+2 |
| | |||||
* | Revert the use of typing_extensions in py3.8+ | Michał Górny | 2021-12-01 | 1 | -1/+1 |
| | | | | | | The original change requiring py3.10 TypeGuard (and matching typing_extensions) has been reverted, so revert the requirement on typing_extensions as well. |