Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

godaddy / tartufo Public

Notifications You must be signed in to change notification settings
Fork 74
Star 497

Code
Issues 45
Pull requests 3
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Actually determine if we are dealing with a shallow clone instead of …#298

Merged

sushantmimani merged 3 commits intomaingodaddy/tartufo:mainfrom identify-shallow-clonesgodaddy/tartufo:identify-shallow-clonesCopy head branch name to clipboard

Dec 10, 2021

+23-5

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Dec 10, 2021

Actually determine if we are dealing with a shallow clone instead of assuming
tarkatronic
committed
Switch tests to check the new shallow assumptions
tarkatronic
committed
Mock out is_shallow_clone for all our tests
tarkatronic
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.