chore: rename ./earthly to ./earth and ./earthly-next to ./earth-next

[janishorsts]

Summary by CodeRabbit

• Updates
  • User-facing help, upgrade messages, and status output now refer to the earth command rather than earthly.
  • Build and staging workflows now use earth and earth-next when retrieving binaries and revisions.
  • The version check confirms that earth --version outputs one line beginning with “earth version.”

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: d6f45227-1c8a-47f1-8510-89ed8d962074

📥 Commits

Reviewing files that changed from the base of the PR and between 591c1d8 and 5b0744f.

📒 Files selected for processing (8)

• .github/actions/stage2-setup/action.yml
• .github/workflows/build-earthly.yml
• .github/workflows/ci-staging-deploy.yml
• .github/workflows/ci.yml
• Earthfile
• cmd/earth/flag/global.go
• earth
• earth-next

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The changes replace earthly and earthly-next references with earth and earth-next in wrapper text, build scripts, and CI workflows. The workflows update binary retrieval and next-client SHA reads, including BuildKit and ticktock revision reads. Existing checks and the staging workflow output key remain unchanged.

Changes

Earth command and next-client naming

Layer / File(s)	Summary
Earth command and script references Earthfile, earth, cmd/earth/flag/global.go	Script checks and prerelease artifact creation use ./earth. Wrapper text and a flag comment identify the earth command.
Staging setup and deployment .github/actions/stage2-setup/action.yml, .github/workflows/ci-staging-deploy.yml	The workflows invoke ./earth upgrade and read the expected client SHA from earth-next. The staging workflow output key remains earthly_next.
Next-client revision reads .github/workflows/build-earthly.yml, .github/workflows/ci.yml, Earthfile	Build workflows and the ticktock target read revisions from earth-next. The BuildKit update conditions and invocation remain unchanged.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 5b074

Scripts and workflows use the renamed earth and earth-next paths, and staging still passes the revision to its consumer. No actionable merge risk remains.

Security Architecture Review

Security architecture risk: ⚪ Minimal · up to 5b074

The renamed commands and revision file remain aligned with their build and release consumers. The change does not alter the inspected credential namespaces, permissions, installation destinations, or update behavior. No introduced or worsened security risk was identified.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — The affected execution remains within the existing developer-wrapper and CI/release contexts, including their existing container-engine and optional sudo authority. The inspected rename does not extend access to another tenant, credential namespace or deployment environment.

Trust Boundaries and Controls

• observed — The changed acquisition step remains gated to non-fork runs. USE_NEXT retains its nonempty revision check and embedded-SHA search, and the BuildKit workflow retains its registry-login gate. These controls are unchanged; the embedded-SHA search is a consistency check, not proof of artifact authenticity.

Resilience and Maintainability Implications

• inferred — Keeping the wrapper's internal storage and extraction paths unchanged preserves compatibility with the CI steps that move its downloaded binary. No new cleanup-ownership or recovery mismatch was identified from the rename.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: renaming ./earthly to ./earth and ./earthly-next to ./earth-next across scripts, workflows, and documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🎉 Are we earthbuild yet?

Great progress! You've reduced "earthly" occurrences by 32 (1.16%)

📈 Overall Progress

Branch	Total Count
main	2754
This PR	2722
Difference	-32 (1.16%)

📁 Changes by file type:

File Type	Change
Go files (.go)	✅ -1
Documentation (.md)	➖ No change
Earthfiles	✅ -12

---

Keep up the great work migrating from Earthly to Earthbuild! 🚀

💡 Tips for finding more occurrences

Run locally to see detailed breakdown:

./.github/scripts/count-earthly.sh

Note that the goal is not to reach 0.
There is anticipated to be at least some occurrences of earthly in the source code due to backwards compatibility with config files and language constructs.