Closed r0mainK closed 6 years ago
@r0mainK what is the bug exactly? I see no problems in your listing.
The typo was: COMMIT_MESSAGES["initilialize"]
in the index's reset
.
Also, the doc in dulwich was bad, it said dulwich' add acted like git add --all
when in fact it was just adding untracked files -> so all unstaged files, deleted or modified, were not: nothing happened when doing the reset
. Also, the commit would default to CWD, so before it could commit on another repo. I didn't see all this until yesterday, most of the tests I'd done when playing with dulwich were done while it was bugged (actually still is but my PRs should fix it when merged), and without considerations like same/different CWD, untracked/unstaged files, etc.
Oh and there was a typo in _are_local_and_remote_heads_different
, because I assumed the head
method of Repo
was a property, which it was not.
Just a typo I did not see, there might be a couple of those - btw once everything has been tested for real, i think we should release a new version. However, currently it does not work, because dulwich is bugged:
I will work on it monday, during OSD.