feat: fold export/import under a bundle noun#12
Merged
Conversation
BREAKING (pre-1.0, no alias): `ferry export` / `ferry import` become `ferry bundle export` / `ferry bundle import`. Flags (--out, --include-local, --expect-sha256) and behaviour are unchanged — only the command path moves under a `bundle` parent noun, matching how git groups `git bundle` subcommands and reclaiming two top-level slots. `bundle` joins `agents` as a grouped-operation noun. Runtime hints and Long docs that named `ferry import` now name `ferry bundle import`; the CLI reference is regenerated. Recorded under the CHANGELOG Breaking section.
# Conflicts: # CHANGELOG.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
BREAKING (pre-1.0, no deprecation alias): folds the top-level
exportandimportcommands under a newbundleparent noun.ferry export→ferry bundle exportferry import <bundle>→ferry bundle import <bundle>Flags (
--out,--include-local,--expect-sha256) and all behaviour areunchanged — only the command path moves. This matches how git groups
git bundle create/verify/unbundleunder one noun, reclaims two top-level slots,and gives a future
bundle verifyan obvious home.bundlejoinsagentsas agrouped-operation noun.
Changes
cmd/bundle.goparent noun (modelled oncmd/agents.go);export/importreparented under it and removed from the root command.
Longdocs that namedferry importnow nameferry bundle import.bundleadded todocumentedCommands;the reachability check retargeted to assert
ferry --helplistsbundleandferry bundle --helplistsexport/import.commands.md,getting-started.md,configuration.md)updated; CLI reference regenerated (
make gen-docs).Breakingentry added.Verified
make build,gofmt -l .(empty),go vet ./...,go test ./..., and the fulleval suite (
FERRY_BIN=… go test ./evals/) all green. Behaviourally:ferry exportnow errorsunknown command,ferry --helplistsbundle, andferry bundle --helplistsexport/import.