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

magefile / mage Public

Notifications You must be signed in to change notification settings
Fork 256
Star 4.2k

Code
Issues 88
Pull requests 32
Discussions
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security
Insights

Rely on GOCACHE rather than our own hashing mechanism#168

Merged

natefinch merged 5 commits intomastermagefile/mage:masterfrom use-gocachemagefile/mage:use-gocacheCopy head branch name to clipboard

Sep 19, 2018

+254-52

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Sep 18, 2018

use gocache and add some debug timing logs
natefinch
committed
only check for files in cache_dir
natefinch
committed

Commits on Sep 19, 2018

clean up the code and fix deferred removal
natefinch
committed
add test for gocache use
natefinch
committed
make sure clean gets the main files too
natefinch
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.