Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shallow clone detection (or depth) #56

Open
giarve opened this issue Oct 26, 2024 · 2 comments
Open

Shallow clone detection (or depth) #56

giarve opened this issue Oct 26, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@giarve
Copy link

giarve commented Oct 26, 2024

There are many times when we perform a shallow clone, and later we use the tool without realizing we are only taking N last commits but not the whole commit history since when the module was added.

Maybe a confirmation alert (answer y/n) would be better than performing a full clone without asking first.

@giarve giarve added the enhancement New feature or request label Oct 26, 2024
@sebalix
Copy link
Collaborator

sebalix commented Nov 4, 2024

Good point. Should we block fully the use of the tool on such cloned repository? A warning+confirmation is probably not enough if we want to prevent the opening of PRs on OCA with limited commits history.

@sebalix
Copy link
Collaborator

sebalix commented Nov 21, 2024

Putting that here: https://stackoverflow.com/questions/37531605/how-to-test-if-git-repository-is-shallow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants