Implements MIL-004: the project details can be set in config.env, and a detail that is set there is not asked.
Eight optional keys: PROJECT_NAME, PROJECT_DESCRIPTION, PROJECT_VISIBILITY, GITEA_OWNER, USE_GITHUB, GITHUB_OWNER, PROJECT_DIRECTORY, ENABLE_PLAN_GATE, checked with the validators the prompts use
A key that is present counts as set (only the description may be empty); the summary marks it (from config.env)
An invalid value stops the run before any request and names the key; it never falls back to asking
USE_GITHUB=no skips the GitHub owner; a stray GITHUB_OWNER is ignored with a warning
The confirmations (create now, reuse, directory, hooks path, templates) stay interactive and default to no
Keys documented in config.env.example and the README; new keys are rejected in .env
A value containing # must be quoted (documented and tested), because an unquoted # starts a comment
config.env is now ignored by git
Review and tests
Code review recorded as RC-019 (Go). Findings F1 and F2 were fixed; F3 (noisy summary markers) and F4 (the constant PROJECT_NAME shares a name with the new key) are recorded and not blocking
Tests: tests/test-presets.sh; full suite 923 checks, 0 failed; mutation check done
The branch is stacked on mil-004-plan (PR 32), which is stacked on mil-003-scaffold-and-release, so the diff shows only this change. Retarget when those merge.
Implements MIL-004: the project details can be set in `config.env`, and a detail that is set there is not asked.
- Eight optional keys: `PROJECT_NAME`, `PROJECT_DESCRIPTION`, `PROJECT_VISIBILITY`, `GITEA_OWNER`, `USE_GITHUB`, `GITHUB_OWNER`, `PROJECT_DIRECTORY`, `ENABLE_PLAN_GATE`, checked with the validators the prompts use
- A key that is present counts as set (only the description may be empty); the summary marks it `(from config.env)`
- An invalid value stops the run before any request and names the key; it never falls back to asking
- `USE_GITHUB=no` skips the GitHub owner; a stray `GITHUB_OWNER` is ignored with a warning
- The confirmations (create now, reuse, directory, hooks path, templates) stay interactive and default to no
- Keys documented in `config.env.example` and the README; new keys are rejected in `.env`
- A value containing ` #` must be quoted (documented and tested), because an unquoted ` #` starts a comment
- `config.env` is now ignored by git
Review and tests
- Code review recorded as RC-019 (Go). Findings F1 and F2 were fixed; F3 (noisy summary markers) and F4 (the constant `PROJECT_NAME` shares a name with the new key) are recorded and not blocking
- Tests: `tests/test-presets.sh`; full suite 923 checks, 0 failed; mutation check done
The branch is stacked on `mil-004-plan` (PR 32), which is stacked on `mil-003-scaffold-and-release`, so the diff shows only this change. Retarget when those merge.
Closes #27
Closes #28
Closes #29
Closes #30
Closes #31
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Eight optional keys (PROJECT_NAME, PROJECT_DESCRIPTION, PROJECT_VISIBILITY,
GITEA_OWNER, USE_GITHUB, GITHUB_OWNER, PROJECT_DIRECTORY, ENABLE_PLAN_GATE)
are read and checked with the validators the prompts use. A key that is
present counts as set (only the description may be empty); it is not asked
and the summary marks it "(from config.env)". An invalid value stops the
run before any request and names the key. USE_GITHUB=no skips the GitHub
owner and warns about a stray GITHUB_OWNER. The confirmations stay
interactive. Keys and an example are documented; tests cover every key.
Task: MIL-004#1
Task: MIL-004#2
Task: MIL-004#3
Task: MIL-004#4
Task: MIL-004#5
Closes#27Closes#28Closes#29Closes#30Closes#31
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Tirsvad
merged commit fb6c439325 into mil-004-plan2026-10-05 17:06:37 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Implements MIL-004: the project details can be set in
config.env, and a detail that is set there is not asked.PROJECT_NAME,PROJECT_DESCRIPTION,PROJECT_VISIBILITY,GITEA_OWNER,USE_GITHUB,GITHUB_OWNER,PROJECT_DIRECTORY,ENABLE_PLAN_GATE, checked with the validators the prompts use(from config.env)USE_GITHUB=noskips the GitHub owner; a strayGITHUB_OWNERis ignored with a warningconfig.env.exampleand the README; new keys are rejected in.env#must be quoted (documented and tested), because an unquoted#starts a commentconfig.envis now ignored by gitReview and tests
PROJECT_NAMEshares a name with the new key) are recorded and not blockingtests/test-presets.sh; full suite 923 checks, 0 failed; mutation check doneThe branch is stacked on
mil-004-plan(PR 32), which is stacked onmil-003-scaffold-and-release, so the diff shows only this change. Retarget when those merge.Closes #27
Closes #28
Closes #29
Closes #30
Closes #31
🤖 Generated with Claude Code