Skip to content

DRAFT: Feature/50 fix toc#62

Closed
danielschlegel wants to merge 5 commits into
mainfrom
feature/50-fix-toc
Closed

DRAFT: Feature/50 fix toc#62
danielschlegel wants to merge 5 commits into
mainfrom
feature/50-fix-toc

Conversation

@danielschlegel
Copy link
Copy Markdown
Collaborator

Summary of Changes

This appears to be a major rebranding effort from "Earthly" to "Earthbuild". Here are the key changes:

1. Brand/Name 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

2. Configuration and CI/CD Updates

  • 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

3. Documentation Changes

  • Extensive updates to README files across the project
  • Updated installation instructions and examples
  • Changed documentation references throughout
  • Updated changelog to reflect the rebranding

4. File Removals and Cleanup

  • Deleted various configuration files (like .earthly_version_flag_overrides, .earthlyignore)
  • Removed cloud-related documentation and features
  • Cleaned up various CI configuration files

5. Recent Commits Show

6. Key Infrastructure Changes

  • 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.

- Updated all references from "Earthly" to "EarthBuild" in headers,
  descriptions, and documentation
- Changed section headers like "Why Use Earthly?" to "Why Use
  EarthBuild?"
- Updated all product descriptions and feature explanations

- Removed "Earthly Satellites" references
- Changed "🔑 Cloud secrets support built-in" to "🔑 Secrets support
  built-in"
- Removed references to "Earthly remote BuildKits" and replaced with
  generic "remote BuildKits"

- Removed clickable links to earthly.dev
- Updated installation references to point to local installation
  instructions
- Removed badges linking to earthly.dev documentation and slack
- Updated the logo reference to remove the earthly.dev link

- Changed from `github.com/earthly/earthly` to
  `github.com/EarthBuild/earthbuild`
- Updated CI badge links, issue reporting links, and example repository
  references
- Updated command examples to use `earthbuild` instead of `earthly`

- The community fork explanation was already present at the top and is
  well-maintained
- Preserved the historical context and links to the original Earthly
  project for transparency

- Replaced specific earthly.dev documentation links with "documentation
  coming soon" placeholders
- Maintained the structure but removed dependencies on the original
  Earthly documentation

- Changed alt text for images from "Earthly" to "EarthBuild"
- Updated button text and installation references
- Updated Docker Hub references while maintaining compatibility

The README now properly reflects EarthBuild as a community fork while
maintaining historical context and removing dependencies on
Earthly-specific infrastructure and cloud services. All links now point
to the EarthBuild organization or are replaced with appropriate
community alternatives.
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.
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a 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 @danielschlegel, 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 represents a comprehensive rebranding and fork of the 'Earthly' project, now named 'Earthbuild'. The changes are pervasive, touching nearly every aspect of the codebase, from build scripts and CI/CD configurations to documentation and core infrastructure. The primary goal is to establish 'Earthbuild' as an independent project, ensuring consistency with the new brand identity across all components.

Highlights

  • Brand/Name Changes: All references to "earthly" have been systematically changed to "earthbuild", including binary names, repository references (e.g., earthly/earthly to earthbuild/earthbuild), organization names, and domain references.
  • Configuration and CI/CD Updates: Updated all BuildKite, CircleCI, and GitHub Actions configurations. Environment variables were changed from EARTHLY_* to EARTHBUILD_*, download URLs were updated, and Docker registry mirrors and authentication settings were modified.
  • Documentation Changes: Extensive updates were made to README files across the project, including installation instructions, examples, and general documentation references. The changelog was also updated to reflect the rebranding.
  • File Removals and Cleanup: Various configuration files, such as .earthly_version_flag_overrides and .earthlyignore, were deleted. Cloud-related documentation and features were removed, and various CI configuration files were cleaned up.
  • Key Infrastructure Changes: Container names were updated from earthly-* to earthbuild-*. Secret organization references, example repository references, and installation/bootstrap scripts were also modified to align with the new brand identity.
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. 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.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a 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 represents a significant rebranding effort from "Earthly" to "Earthbuild". The changes are extensive, affecting configuration files, scripts, source code, and documentation. While the renaming has been carried out thoroughly in most places, I've identified a few potential issues. These include missing configuration files that could break CI pipelines, a typo in a Go struct field name, and some inconsistencies in the renaming of built-in arguments which might lead to confusion. Addressing these points will help ensure the rebranding is complete and correct.

Comment thread .buildkite/windows.yml
EARTHLY_OS: linux
EARTHLY_CONFIG: "./.buildkite/earthly-config-win.yml"
EARTHBUILD_OS: linux
EARTHBUILD_CONFIG: "./.buildkite/earthbuild-config-win.yml"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The configuration file .buildkite/earthly-config-win.yml was removed, but the new file .buildkite/earthbuild-config-win.yml referenced here is not present in the pull request. This will likely cause the Windows build to fail. Please add the new configuration file or remove the reference if it's no longer needed.

Comment thread buildcontext/excludes.go
Comment on lines +13 to +24
const earthbuildIgnoreFile = ".earthbuildignore"
const dockerIgnoreFile = ".dockerignore"

var errDuplicateIgnoreFile = errors.New("both .earthignore and .earthlyignore exist - please remove one")
var errDuplicateIgnoreFile = errors.New("both .earthignore and .earthbuildignore exist - please remove one")

// ImplicitExcludes is a list of implicit patterns to exclude.
var ImplicitExcludes = []string{
".tmp-earthly-out/",
".tmp-earthbuild-out/",
"build.earth",
"Earthfile",
earthIgnoreFile,
earthlyIgnoreFile,
earthbuildIgnoreFile,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The .earthlyignore file was removed in this pull request, but a corresponding .earthbuildignore file was not added. This logic now looks for .earthbuildignore. Without an ignore file, commands like COPY . . might include unintended files (like the build directory or .git), potentially breaking builds or making them less efficient. Please consider adding a .earthbuildignore file with the appropriate exclusion patterns.

Comment thread Earthfile
FROM earthbuild/dind:alpine-3.19-docker-25.0.5-r0
RUN apk add --no-cache --update bash
COPY earthly .earthly_version_flag_overrides .
COPY earthbuild .earthbuild_version_flag_overrides .
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The file .earthly_version_flag_overrides was removed, but the new file .earthbuild_version_flag_overrides referenced here is not added in this pull request. If this file is still needed for feature flags, please add it to avoid potential issues with builds that rely on it.

Comment thread ast/commandflag/flags.go
NoManifestList bool `long:"no-manifest-list" description:"Do not include a manifest list (specifying the platform) in the creation of the image"`
CacheFrom []string `long:"cache-from" description:"Declare additional cache import as a Docker tag"`
WithoutEarthlyLabels bool `long:"without-earthly-labels" description:"Disable build information dev.earthly labels to reduce the chance of changing images digests."`
WithoutearthbuildLabels bool `long:"without-earthbuild-labels" description:"Disable build information dev.earthbuild labels to reduce the chance of changing images digests."`
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There appears to be a typo in the field name WithoutearthbuildLabels. To maintain consistency with Go's camel case naming conventions, it should likely be WithoutEarthbuildLabels.

Suggested change
WithoutearthbuildLabels bool `long:"without-earthbuild-labels" description:"Disable build information dev.earthbuild labels to reduce the chance of changing images digests."`
WithoutEarthbuildLabels bool `long:"without-earthbuild-labels" description:"Disable build information dev.earthbuild labels to reduce the chance of changing images digests."`

@danielschlegel danielschlegel self-assigned this Aug 13, 2025
@kmannislands
Copy link
Copy Markdown

Hey @danielschlegel, thanks for your contribution! I'll close this for now since a wholesale rename is probably too large to merge all at once.

We'll proceed on the renaming with a series of small PRs to do tactical renames in focused areas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants