Save Clayton's Money 💵💵💵

[Byrdman32]

This pull request removes cloning of the LiDAR Submodule hosted via a self-hosted GitLab instance so that Clayton's VPN gets hit with less traffic and as a result saves him money.

[gemini-code-assist]

Summary of Changes

Hello @Byrdman32, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request optimizes the build process for development containers by eliminating the automatic cloning of the Autonomy_Software repository and its submodules. This change is intended to significantly reduce network traffic, particularly for self-hosted GitLab instances and associated VPN usage, thereby decreasing operational costs.

Highlights

• Removed Repository Cloning: The git clone --recurse-submodules command for the Autonomy_Software repository has been removed from both Jammy.dockerfile and JetPack.dockerfile. This change prevents the automatic cloning of this repository and its submodules during the dev container build process.
• Removed Working Directory Setting: The WORKDIR /opt/Autonomy_Software/ command has been removed from both Dockerfiles, as the Autonomy_Software repository is no longer cloned into that path.

Changelog

• .devcontainer/Jammy.dockerfile
  • Removed the RUN git clone --recurse-submodules command for Autonomy_Software.
  • Removed the WORKDIR /opt/Autonomy_Software/ command.
• .devcontainer/JetPack.dockerfile
  • Removed the RUN git clone --recurse-submodules command for Autonomy_Software.
  • Removed the WORKDIR /opt/Autonomy_Software/ command.

Ignored Files

• Ignored by pattern: .github/workflows/** (8)
  • .github/workflows/clang_check.yml
  • .github/workflows/codeql.yml
  • .github/workflows/coverage.yml
  • .github/workflows/deploy_autonomy.yml
  • .github/workflows/deploy_docker.yml
  • .github/workflows/doxygen_generate.yml
  • .github/workflows/help_requester.yml
  • .github/workflows/tests.yml

Activity

• No specific activity (comments, reviews, progress updates) has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request removes the git clone command for the Autonomy_Software repository from the devcontainer Dockerfiles. This is a positive change that aligns with best practices for devcontainers, which typically mount the source code from the host instead of baking it into the image. By removing the repository cloning from the Docker build process, you've correctly addressed the issue of unnecessary submodule cloning, which will reduce build times and avoid potential version conflicts. The changes are sound and improve the devcontainer configuration.