Closed
Description
This is observed using a fresh pipenv with only dulwich==0.18.6 installed using python3.6 from pyenv on OSX
This is obviously not consistent with the way that git itself describes the repository state. Is this by design or a known issue? Are there any known work-arounds? If not I'm happy to give any spare cycles to have a dig into improving things, even if that's just by contributing docs.
bash-3.2$ > ls -l && \
git status && \
python3 -c 'import dulwich.porcelain; print(dulwich.porcelain.status("."))'
total 16
-rw-r--r-- 1 al staff 166 4 Jan 17:50 Pipfile
-rw-r--r-- 1 al staff 1264 4 Jan 17:50 Pipfile.lock
-rw-r--r-- 1 al staff 0 4 Jan 17:46 bar
-rw-r--r-- 1 al staff 0 4 Jan 17:46 foo
On branch master
Changes to be committed:
(use "git reset HEAD <file>..." to unstage)
new file: bar
Untracked files:
(use "git add <file>..." to include in what will be committed)
Pipfile
Pipfile.lock
GitStatus(staged={'add': [b'bar'], 'delete': [], 'modify': []}, unstaged=[], untracked=['bar', 'foo', 'Pipfile', 'Pipfile.lock'])