stale_refs failing due to unhandled "xxxxxx will become dangling!" message

With a repo set up in way that git remote prune --dry-run originreturns the following:

URL: .... my repo utl...
 * [would prune] origin/some-branch
 * [would prune] origin/some-more-branches
 * [would prune] origin/main
 refs/remotes/origin/HEAD will become dangling!

stale_refs throws ValueError: Could not parse git-remote prune result: ' refs/remotes/origin/HEAD will become dangling!'
I suppose this warning message should just silently be skipped at https://github.com/gitpython-developers/GitPython/blob/main/git/remote.py#L614

Don't raise on unknown line when parsing stale refs (#1262)

Thanks for the report. I agree that GitPython reacts a bit strongly to unknown input which can always happen given its source.

Merge pull request #1263 from gitpython-developers/fix-1262

Thanks for the quick reaction 👍

Navigation Menu

Repository navigation

stale_refs failing due to unhandled "xxxxxx will become dangling!" message #1262

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

stale_refs failing due to unhandled "xxxxxx will become dangling!" message #1262

Description

Activity

Byron commented on Jun 3, 2021

afeblot commented on Jun 3, 2021

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions