You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
repo.create_head(branch_name) would be more intuitive as repo.create_branch(branch_name) or repo.branch.create(branch_name)
Merging a branch would be more intuitive as repo.merge(from=branch_name) instead of
# prepare a merge
master = cloned_repo.heads.master # right-hand side is ahead of us, in the future
merge_base = cloned_repo.merge_base(new_branch, master) # allwos for a three-way merge
cloned_repo.index.merge_tree(master, base=merge_base) # write the merge result into index
cloned_repo.index.commit("Merged past and now into future ;)",
parent_commits=(new_branch.commit, master.commit))
It would be nice if you could do repo.head.sha in addition to repo.head.commit.hexsha
Because of the above I switched to repo.git.gitCommand to access the git commands directly.
Thanks for making the gitpython library!
The text was updated successfully, but these errors were encountered:
I agree that the current API is cumbersome to some extend, which is due to GitPython itself being mostly on the level of 'plumbing'. The terms mentioned above as well as the ease at which one can do certain operations are usually implemented in porcelain only.
As GitPython is in maintenance mode, all quality of life improvements must be submitted as a PR, but I think it's OK to keep this issue for ideas.
repo.create_head(branch_name)
would be more intuitive asrepo.create_branch(branch_name)
orrepo.branch.create(branch_name)
Merging a branch would be more intuitive as
repo.merge(from=branch_name)
instead ofIt would be nice if you could do
repo.head.sha
in addition torepo.head.commit.hexsha
Because of the above I switched to repo.git.gitCommand to access the git commands directly.
Thanks for making the gitpython library!
The text was updated successfully, but these errors were encountered: