-
Notifications
You must be signed in to change notification settings - Fork 10
feat: remove CI references to satellites. #24
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
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.
Summary of Changes
Hello @gilescope, I'm Gemini Code Assist1! 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 streamlines the CI/CD configuration and documentation by removing all references and support for 'Satellites' in favor of exclusively using self-hosted Buildkits. This change simplifies the build environment setup and clarifies the recommended approach for remote build execution.
Highlights
- CI Action Simplification: The
stage2-setupGitHub Action has been updated to remove inputs (USE_SATELLITE,SATELLITE_NAME) and associated logic for interacting with 'Satellites', streamlining it to exclusively support self-hosted Buildkits. - Documentation Alignment: All relevant documentation pages have been revised to remove mentions of 'Satellites' and to exclusively promote self-hosted Buildkits as the recommended remote runner solution, simplifying the guidance for users.
- Test Suite Cleanup: Dedicated integration test scripts (
earthly-image-sat.sh,satellites-integration.sh) that specifically tested 'Satellite' functionality have been removed, reflecting the deprecation of this feature from the codebase.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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 or fill out our survey to provide feedback.
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
-
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. ↩
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.
Code Review
This pull request removes references to Earthly Satellites from CI configurations and documentation, focusing instead on self-hosted BuildKits. The changes are generally good and align with the stated goal. I've found a couple of minor issues in the documentation that should be addressed: a typo and a potentially confusing link.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
kmannislands
left a comment
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.
Nice, good to start hacking on the docs too
This appears to be a **major rebranding effort** from "Earthly" to "Earthbuild". Here are the key changes: - All references to "earthly" have been systematically changed to "earthbuild" - Binary name changed from `earthly` to `earthbuild` - Repository references updated from `earthly/earthly` to `earthbuild/earthbuild` - Organization references changed from "earthly-technologies" to "earthbuild-technologies" - Domain references changed from `earthly.dev` to `earthbuild.dev` - Updated all BuildKite, CircleCI, and GitHub Actions configurations - Changed environment variables from `EARTHLY_*` to `EARTHBUILD_*` - Updated download URLs to point to new repository locations - Modified Docker registry mirrors and authentication - Extensive updates to README files across the project - Updated installation instructions and examples - Changed documentation references throughout - Updated changelog to reflect the rebranding - Deleted various configuration files (like `.earthly_version_flag_overrides`, `.earthlyignore`) - Removed cloud-related documentation and features - Cleaned up various CI configuration files - **Latest commit (44d53a6)**: "docs: Summary of Changes Made" - **Previous work included**: - Independent CI setup (#1) - Fork testing for examples (#38) - Removal of satellite CI references (#24) - Complete removal of Cloud features (earthly#4325) - README clarification about fork status (#4) - Updated container names from `earthly-*` to `earthbuild-*` - Changed secret organization references - Updated example repository references - Modified installation scripts and bootstrap processes This represents a **complete fork and rebranding** of the Earthly project to create "Earthbuild" as an independent project. The changes are comprehensive, touching every aspect of the codebase from build scripts to documentation to maintain consistency with the new brand identity.
Leave only references to self hosted buildkits. Fixes #21
Todo: