You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: