Implements MIL-007. Stacked on mil-006-license (PR #52), which is stacked on mil-006-plan (PR #43); retarget as those merge.
After adding or reusing the framework, git submodule update --init --recursive runs, so framework/qc is filled. A failure stops the step and names the command to run by hand.
The script follows links, so a link in a PATH folder works from any folder; the project is created under the folder it is started in.
config.env and .env: --config / --env, else ./config.env and ./.env in the working folder, else the checkout's, each on its own. The files used are named, and a file from the working folder needs a yes (default no) before the first request.
README: where to start the script, a global-command example with its check, the lookup order.
Tests: new tests/test-launch.sh and fixtures for the qc checklists. Full suite: 1031 checks, 0 failed.
Implements MIL-007. Stacked on `mil-006-license` (PR #52), which is stacked on `mil-006-plan` (PR #43); retarget as those merge.
- After adding or reusing the framework, `git submodule update --init --recursive` runs, so `framework/qc` is filled. A failure stops the step and names the command to run by hand.
- The script follows links, so a link in a `PATH` folder works from any folder; the project is created under the folder it is started in.
- `config.env` and `.env`: `--config` / `--env`, else `./config.env` and `./.env` in the working folder, else the checkout's, each on its own. The files used are named, and a file from the working folder needs a yes (default no) before the first request.
- README: where to start the script, a global-command example with its check, the lookup order.
- Tests: new tests/test-launch.sh and fixtures for the qc checklists. Full suite: 1031 checks, 0 failed.
Closes #47
Closes #48
Closes #49
Closes #51
- git submodule update --init --recursive after adding or reusing the framework
- Follow links to the script so SCRIPT_DIR and the checkout are the real ones
- config.env and .env: --config/--env, else ./ in the working folder, else the checkout's
- Name the files used; a file from the working folder needs a yes before any request
- MIL-007 accepted; test fixtures for the qc checklists; tests/test-launch.sh
Work in progress: the README section is not written yet, and four tests of
test-launch.sh fail and two shellcheck warnings remain; they are fixed next.
Task: MIL-007#1
Task: MIL-007#2
Refs #47
Refs #48
Refs #51
- README: start from the folder where the project is created, make the script a global command, where config.env and .env are read from and the confirmation
- Tests: qc tests set up the temp directory and force a real failure; the default-files test runs from a folder without files of its own; the link test allows for path aliases; the work directory cleanup deletes links
Task: MIL-007#3
Task: MIL-007#4
Refs #49
Refs #51
Tirsvad
merged commit fcc155a8ff into mil-006-license2026-10-07 08:17:23 +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-007. Stacked on
mil-006-license(PR #52), which is stacked onmil-006-plan(PR #43); retarget as those merge.git submodule update --init --recursiveruns, soframework/qcis filled. A failure stops the step and names the command to run by hand.PATHfolder works from any folder; the project is created under the folder it is started in.config.envand.env:--config/--env, else./config.envand./.envin the working folder, else the checkout's, each on its own. The files used are named, and a file from the working folder needs a yes (default no) before the first request.Closes #47
Closes #48
Closes #49
Closes #51