Docker COPY with checkout fetch-depth: 0

[glenn-jocher]

🤖 Generated by Copilot at 8a54701

Summary

📦🚚🔧

This pull request modifies the Docker-related files and workflows to copy the current state of the repository to the Docker images, instead of cloning the latest version from GitHub. This allows the Docker images to access the full git history and to match the exact codebase of the repository.

fetch-depth is zero
copying the whole repo
winter of Docker

Walkthrough

• Copy the current repository contents to the Docker images instead of cloning from GitHub ([link](https://github.com/ultralytics/yolov5/pull/12066/files?diff=unified&w=0#diff-140b4a4c490ff4b325ebe28803157cc59f3b3894af1a98d79ca990bda7877448L27-R27), [link](https://github.com/ultralytics/yolov5/pull/12066/files?diff=unified&w=0#diff-d98329d5cefd0fb8ae8f592080ecfdbe8e4893a909df08623bf372f53508107eL30-R30), [link](https://github.com/ultralytics/yolov5/pull/12066/files?diff=unified&w=0#diff-153cb5313e95fd4c232ca740bff18b6f1b2a9864cb3558125996aded94177f54L33-R33)). This ensures consistency and accuracy of the Docker images with the repository state at the time of the workflow run. The files affected are utils/docker/Dockerfile, utils/docker/Dockerfile-arm64, and utils/docker/Dockerfile-cpu.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Optimization of Docker builds for the YOLOv5 project by including the full git history.

📊 Key Changes

• Updated GitHub Actions workflow to fully fetch the git history (fetch-depth: 0).
• Modified Dockerfiles to copy the local repository content directly instead of cloning from GitHub.

🎯 Purpose & Impact

• Ensure consistency: By copying the entire repository (including its git history) into the Docker image, this creates a more consistent and traceable build environment.
• Reduce errors: Direct copying mitigates issues related to the absence of a .git directory that could occur when cloning.
• Speed up builds: This change could potentially speed up the Docker build process by using the local copy of the codebase rather than fetching it anew.
• Impact on users: Users may notice more reliable and faster builds when using Docker images containing the YOLOv5 environment.