Skip to content

fix: should not throw error on any shallow cloned repo#7475

Merged
abeizn merged 1 commit into
mainfrom
kw-7468-gitext-empty-repo
May 16, 2024
Merged

fix: should not throw error on any shallow cloned repo#7475
abeizn merged 1 commit into
mainfrom
kw-7468-gitext-empty-repo

Conversation

@klesh
Copy link
Copy Markdown
Contributor

@klesh klesh commented May 16, 2024

Summary

fix: should not throw error on any shallow cloned repo

Does this close any open issues?

Closes #7468

@klesh klesh force-pushed the kw-7468-gitext-empty-repo branch from 1014b24 to 102720c Compare May 16, 2024 07:02
@abeizn abeizn merged commit 153f7b9 into main May 16, 2024
@abeizn abeizn deleted the kw-7468-gitext-empty-repo branch May 16, 2024 07:09
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.

[Bug][GitHub] GitExtractor fails on empty repository due to shallow clone

2 participants