FazBrowse GitHub Viewer
|
Trending
|
URL:
|
Home
Tools:
[Download Repo ZIP]
[Original HTTPS Page]
`repo.blame` and `repo.blame_incremental` now accept `None` as the `rev` parameter. by Gaubbe · Pull Request #1846 · gitpython-developers/GitPython · GitHub
gitpython-developers
GitPython
Repository navigation
Code
Issues
1
(1)
Pull requests
Discussions
Actions
Security and quality
42
(42)
Insights
repo.blame and repo.blame_incremental now accept None as the rev parameter.
- #1846
#1846
Merged
Byron
merged 3 commits into
gitpython-developers:main
gitpython-developers/GitPython:main
from
Gaubbe:main
Gaubbe/GitPython:main
Copy head branch name to clipboard
Feb 26, 2024
Conversation
Commits
3
(3)
Checks
Files changed
Merged
repo.blame and repo.blame_incremental now accept None as the rev parameter.
#1846
Byron
merged 3 commits into
gitpython-developers:main
gitpython-developers/GitPython:main
from
Gaubbe:main
Gaubbe/GitPython:main
Copy head branch name to clipboard
Commits
Commits on Feb 24, 2024
fix: both blame methods accept None as a revision
Gaubbe
committed
f2e35e7
View commit details
Copy full SHA for f2e35e7
Browse repository at this point
fix: branch now up to date with upstream
Gaubbe
committed
bbabcdc
View commit details
Copy full SHA for bbabcdc
Browse repository at this point
Commits on Feb 25, 2024
docs: updated explanation of the `rev` parameter for both blame methods
Gaubbe
committed
27d8a14
View commit details
Copy full SHA for 27d8a14
Browse repository at this point
Back
|
FazBrowse Home
|
New Git URL