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
+29-35Lines changed: 29 additions & 35 deletions
Original file line number
Diff line number
Diff line change
@@ -62,41 +62,6 @@ Follow linked crate name for detailed status. Please note that all crates follow
62
62
63
63
[semver]: https://semver.org
64
64
65
-
### Pipeline Integration
66
-
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
-
69
-
#### Pipeline Integration - building the base image (when speed matters)
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