feat!: rename workspace manifest to batchspace - #17
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 12184659bf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| /// 工作区清单的固定文件名。 | ||
| pub const WORKSPACE_FILE: &str = "workspace.toml"; | ||
| pub const WORKSPACE_FILE: &str = "batchspace.toml"; |
There was a problem hiding this comment.
When an upgraded workspace still contains only workspace.toml, manifest-creating paths now treat it as a new workspace: scan calls read_or_new and unconditionally writes the new filename, while a successful clone does the same. Consequently, running batch-git scan can leave both files present—even creating an empty batchspace.toml when repository inspection fails—and subsequent commands then ignore the existing repository metadata and schedules. Refuse creation when the legacy file exists and instruct the user to rename it explicitly, without reading or migrating it automatically.
AGENTS.md reference: AGENTS.md:L12-L12
Useful? React with 👍 / 👎.
| ### Added | ||
|
|
||
| - Added `batch-git merge --default` (short option `-d`), reading each repository's `default_branch` from `workspace.toml` and merging it into the current branch. Multi-component names are supported; when no local branch exists, resolution falls back only to that repository's `primary_remote` and does not fetch implicitly. | ||
| - Added `batch-git merge --default` (short option `-d`), reading each repository's `default_branch` from `batchspace.toml` and merging it into the current branch. Multi-component names are supported; when no local branch exists, resolution falls back only to that repository's `primary_remote` and does not fetch implicitly. |
There was a problem hiding this comment.
The entries under versions 0.3.0, 0.2.0, and 0.1.0 describe binaries that only recognized workspace.toml, so rewriting those already-released sections to say batchspace.toml makes the historical changelog factually incorrect. Users consulting these entries while running or diagnosing an older binary will be told to use a filename that version cannot discover; retain workspace.toml in pre-1.0 release notes and document the rename only under 1.0.0.
Useful? React with 👍 / 👎.
| [Semantic Versioning](https://semver.org/). See `Cargo.toml` for the current package version. | ||
|
|
||
| ## [Unreleased] | ||
| ## [1.0.0] - 2026-08-07 |
There was a problem hiding this comment.
Relabeling the existing section as 1.0.0 removes the changelog's only Unreleased heading, even though the file still defines an [Unreleased] comparison link and docs/DEVELOPMENT.md plus CONTRIBUTING.md require future public changes to be recorded in that section. Without an empty heading above 1.0.0, subsequent changes either have no prescribed destination or get appended to an already released version, corrupting future release notes; keep an empty ## [Unreleased] section in both language versions.
Useful? React with 👍 / 👎.
1 participant
Summary
workspace.tomltobatchspace.toml.1.0.0, with synchronized English/Chinese docs and automation guidance.Validation
cargo fmt -- --checkcargo test --lockedcargo clippy --all-targets --all-features -- -D warningscargo build --locked --releaseMigration
Users must explicitly run
mv workspace.toml batchspace.tomlbefore upgrading.