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
Copy file name to clipboardExpand all lines: README.md
+21-11Lines changed: 21 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -64,27 +64,37 @@ Follow linked crate name for detailed status. Please note that all crates follow
64
64
65
65
### Pipeline Integration
66
66
67
-
Some CI/CD pipelines leverage repository cloning. Below is a copy-paste-able example to build docker images for such workflows.
67
+
Some CI/CD pipelines leverage repository cloning. Below is a copy-paste-able example to build docker images for such workflows. As no official image exists (at this time), one must first be built.
68
68
69
-
#### Pipeline Integration (recommended)
69
+
#### Pipeline Integration - building the base image (when speed matters)
70
70
71
-
Build an image without a target and then copy the binaries into your local image
Once a docker image is built there are 2 options. One can replace `FROM alpine:latest` (or `FROM debian:bookworm-slim`) with `FROM gitoxide:latest`, or the resulting binaries can be copied into an existing `Dockerfile` and leveraged as a drop-in replacement for `git clone` directives.
82
+
83
+
#### Pipeline Integration - minimal
84
+
85
+
For example, if a `Dockerfile` currently uses something like `RUN git clone https://github.com/Byron/gitoxide`, first build the minimal image:
0 commit comments