- Notifications
You must be signed in to change notification settings - Fork1k
chore(docs): add recommendations for dependency management#13400
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
reads like a best-selling novel. thank you@johnstcn
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Awesome.
| providers. | ||
| - **Improve build performance:** Coder caches provider versions on each build. | ||
| If the same provider version can be re-used on subsequent builds, Coder will | ||
| simply re-use the cached version if it is available. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
We could explicitly state that cache utilization is only possible when a lock-file is present. I could be misremembering, but providers will always be re-downloaded otherwise, even if cached.
No description provided.