Resolve source operations from the Git checkout root
This commit is contained in:
@@ -21,8 +21,9 @@ go run ./cmd/releasekit check [--repo DIR] [--config FILE] VERSION
|
||||
```
|
||||
|
||||
`VERSION` must use stable `vMAJOR.MINOR.PATCH` syntax. Options must precede the
|
||||
version. The repository defaults to the current directory, and the profile
|
||||
defaults to `<repository>/releasekit.json`. A successful command prints the
|
||||
version. The repository argument defaults to the current directory. ReleaseKit
|
||||
resolves its containing Git checkout root before selecting the module or profile;
|
||||
the profile defaults to `<repository-root>/releasekit.json`. A successful command prints the
|
||||
captured module, version, full tag, and commit. It checks the committed release note and
|
||||
local Git state, runs the standard offline Go test suite (with `-race` when
|
||||
`validation.go.race` is true), and runs a separate `go vet -mod=readonly ./...`
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
# Configuration
|
||||
|
||||
ReleaseKit reads a JSON profile from `<repository>/releasekit.json` by default.
|
||||
The repository directory defaults to the current directory. A relative profile
|
||||
path is resolved from that repository directory; an absolute path is used as-is.
|
||||
ReleaseKit reads a JSON profile from `<repository-root>/releasekit.json` by default.
|
||||
The repository argument defaults to the current directory; the CLI resolves its
|
||||
containing Git checkout root. A relative profile path is resolved from that root;
|
||||
an absolute path is used as-is.
|
||||
|
||||
The current profile fields are:
|
||||
|
||||
|
||||
@@ -24,7 +24,14 @@ review gates. Add focused completion markers as issues are resolved.
|
||||
|
||||
## Issue 1: Resolve the actual Git repository root before release identity (P1)
|
||||
|
||||
Status: open. Category: architecture gap and incorrect publication.
|
||||
Status: complete. Category: architecture gap and incorrect publication.
|
||||
|
||||
**Completion:** Source operations and CLI profile selection resolve the containing
|
||||
Git checkout root before module selection. Regression tests verify that a child
|
||||
directory cannot bypass a failing root suite or publish its tag, explicit nested
|
||||
selection binds its own source and tag, aliases and independent worktrees retain
|
||||
their identity, and dependency preparation works without Git. The focused public
|
||||
API tests and candidate, delivery, CLI, and profile suites pass offline.
|
||||
|
||||
**Evidence:** [candidate capture](../../internal/candidate/check.go) treats
|
||||
`filepath.Abs(request.RepositoryDir)` as the repository root, and
|
||||
|
||||
Reference in New Issue
Block a user