2026-10-03 - 2026-10-06
Overview
10 Pull requests merged by 1 user
Merged
#34 MIL-004: project details preset in config.env (with the e2e fixes and the plan)
Merged
#33 MIL-004: project details preset in config.env
Merged
#32 Plan MIL-004: project details preset in config.env
Merged
#26 MIL-003: local project, framework submodule, hooks, templates and README
Merged
#25 MIL-002: GitHub and Gitea steps (dry run, repositories, push mirror) and split into library files
Merged
#24 MIL-001 review fixes: stop tokens leaking under bash -x, move script to src/, RC-016
Merged
#22 MIL-001 Foundation: config parsing, HTTP helper, prompts and tests
Merged
#21 Link synced milestones in the project plan
Merged
#2 Plan RepoFoundry: baseline, UC-001 artifacts and reviews
Merged
#1 Plan RepoFoundry: business case, stakeholders, plan, milestones, UC-001
11 Issues closed from 1 user
Closed
#28 Use configured details instead of asking, and show their source
Closed
#29 Keep the confirmations interactive
Closed
#30 Document the keys
Closed
#31 Test every key and case
Closed
#27 Read and validate the eight optional config keys
Closed
#8 .gitignore and test harness
Closed
#7 Interactive prompts and input validation
Closed
#4 Script skeleton with strict mode and safe helpers
Closed
#5 Safe parser for config.env and .env
Closed
#6 Tool check and HTTP helper
Closed
#3 Define project name and configuration files
23 Issues created by 1 user
Opened
#3 Define project name and configuration files
Opened
#4 Script skeleton with strict mode and safe helpers
Opened
#5 Safe parser for config.env and .env
Opened
#6 Tool check and HTTP helper
Opened
#7 Interactive prompts and input validation
Opened
#8 .gitignore and test harness
Opened
#9 Preflight checks before any creation
Opened
#10 Create the empty GitHub repository (optional)
Opened
#11 Create the Gitea repository, with AGPL license when GitHub is chosen
Opened
#12 Configure the Gitea to GitHub push mirror (when GitHub is chosen)
Opened
#13 Partial-failure reporting and resume
Opened
#14 Document token permissions and API limitations
Opened
#15 Create the local project directory and credential-free remotes
Opened
#16 Add the framework submodule
Opened
#17 Install skills and git hooks, with optional plan gate
Opened
#18 Copy the framework templates without overwriting
Opened
#19 Write README.md
Opened
#20 End-to-end test and final security review
Opened
#27 Read and validate the eight optional config keys
Opened
#28 Use configured details instead of asking, and show their source
Opened
#29 Keep the confirmations interactive
Opened
#30 Document the keys
Opened
#31 Test every key and case