-
Notifications
You must be signed in to change notification settings - Fork 3
readme: key advantages #61
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
Conversation
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
| * **Optimized cache warming & reuse.** | ||
| The builder can use the GitHub Actions cache backend to persist layers across | ||
| branches, PRs, and rebuilds. This significantly reduces cold-start times and | ||
| avoids repeating expensive dependency installations, even for external | ||
| contributors' pull requests. |
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.
| ## Usage | ||
| ### Build reusable workflow |
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.
Maybe we could clarify the difference here, eg in case one is not familiar with bake.
| ### Build reusable workflow | |
| ### build.yml workflow example | |
| Use this workflow for standard image builds using a Dockerfile. |
And similarly for the other section:
### bake.yml workflow example
Use this workflow for builds that use [Bake](https://docs.docker.com/build/bake/)
to define multiple build targets.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.
Good point, didn't want to expand on Usage section yet as we are still working on UX (related to #55) but I agree that we should improve it. I think this is fine for a follow-up.
No description provided.