Skip to content

Conversation

@brendan-kellam
Copy link
Contributor

@brendan-kellam brendan-kellam commented Sep 8, 2025

For certain repos, re-indexing would fail when calling git fetch with error message fatal: couldn't find remote ref HEAD. The theory is that while we did have a refspec for remote.origin.fetch, it was not being resolved since we were fetching against the remote url and not origin. The solution is to specify the refspec inline with the fetch command.

Fixes #492

@coderabbitai
Copy link

coderabbitai bot commented Sep 8, 2025

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch bkellam/fix_492

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

This comment has been minimized.

@brendan-kellam
Copy link
Contributor Author

brendan-kellam commented Sep 8, 2025

@musabshak do you mind pasting the error message you were seeing during fetch so I can include it in the PR description? Nvm it's in the issue 😅

@brendan-kellam brendan-kellam merged commit b05fc7a into main Sep 8, 2025
8 checks passed
@brendan-kellam brendan-kellam deleted the bkellam/fix_492 branch September 8, 2025 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Git repo state seems to be corrupt?

2 participants