I'm trying to run git bug bridge pull but it fails with:

Error: can't read configured bridges: branch config: invalid merge

$ git bug version
git-bug version: 0.7.1-dev-663c429605

I'm running this in a repository where I once ran an old (0.4.0?) version of git-bug; but attempted to clean out.

git for-each-ref refs/ # shows no identities or bugs
rm -rf .git/git-bug

This seems to be caused by the following piece of the repository's .git/config:

[branch "refs/pull/6952/head"]
	remote = origin
	merge = refs/pull/6952/head

For some reason, git-bug doesn't like that value for merge.

Possible a go-git bug as a similar looking issue is posted at https://github.com/go-git/go-git/issues/331

This is indeed the problem, also mentioned in https://github.com/go-git/go-git/issues/530

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue

github-actions (github-actions) added label lifecycle/stale 2 years ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/rotten 1 year ago

github-actions (github-actions) removed label lifecycle/stale 1 year ago

sudoforge removed label lifecycle/dormant 10 months ago

sudoforge added label kind/bug 10 months ago

sudoforge added label area/git 10 months ago

sudoforge added label root-cause/go-git 10 months ago

sudoforge removed label root-cause/go-git 10 months ago

I just ran into this issue, having a branch with merge = .../pull/....
Such branches might be created by gh pr checkout NNN which is a common command in my workflows.

I could resolve the problem by asking Google AI, but maybe a better error message would help here. My .git/config has >500loc, so it is hard to find the problem without any more specific error, or at least a line number...