2026-10-05 - 2026-10-12
Overview
3 Releases published by 1 user
Published
v0.3.3
RepoFoundry 0.3.3
Published
v0.3.2
RepoFoundry 0.3.2
Published
v0.3.1
RepoFoundry 0.3.1
26 Pull requests merged by 1 user
Merged
#80 Rename the wiki pages without hyphens
Merged
#79 Use the kebab-case repository name
Merged
#78 Add the wiki, Quality and Release workflows
Merged
#76 Run the shared quality checks on pull requests
Merged
#75 Bump the framework to v0.5.0 and the version to 0.3.3
Merged
#74 Bump the version to 0.3.2 (task 5)
Merged
#73 Test the Git excludes step (task 4)
Merged
#72 Describe the files git ignores in the README (task 3)
Merged
#71 Accept MIL-009 and add the Git excludes step (task 2)
Merged
#70 Plan MIL-009: .claude, .agents and AGENTS.md are excluded from git
Merged
#64 Link the token how-to from the README credentials section
Merged
#63 Add a step-by-step how-to for the Gitea and GitHub tokens
Merged
#58 Gitea is the only remote (MIL-008) and version 0.3.1
Merged
#57 Docs: record S02's acceptance of RC-022 to RC-030
Merged
#56 Docs: record the user-owner end-to-end run (A2) in RC-017
Merged
#55 Docs: .env is optional, config.env is required (UC-002, US-002, OC-002, DCD, MIL-007) and review RC-030
Merged
#54 Implement MIL-006 and MIL-007: project license, qc submodules, link start, default configuration files
Merged
#52 Implement MIL-006: project license in config.env; AGPL-3.0 default only for a public GitHub project
Merged
#53 Implement MIL-007: qc submodules fetched, start through a link, default configuration files
Merged
#43 Plan MIL-006 and MIL-007 and UC-002: public-only AGPL default, qc fetch, global command
Merged
#42 Plan MIL-006: the project license set in config.env
Merged
#41 MIL-005: ask for missing credentials and create the project's own .env
Merged
#40 Add the Design Class Diagrams and plan MIL-005 (credentials asked, project .env)
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
39 Issues closed from 1 user
Closed
#69 Bump the version to 0.3.2
Closed
#68 Test the excludes
Closed
#67 Describe the excluded files in the README
Closed
#66 Add the Git excludes step
Closed
#65 Update the analysis and design documents
Closed
#61 Test the single remote
Closed
#62 Bump the version to 0.3.1
Closed
#59 Add only the origin remote
Closed
#60 Describe the one remote in the README
Closed
#20 End-to-end test and final security review
Closed
#19 Write README.md
Closed
#18 Copy the framework templates without overwriting
Closed
#17 Install skills and git hooks, with optional plan gate
Closed
#16 Add the framework submodule
Closed
#15 Create the local project directory and credential-free remotes
Closed
#14 Document token permissions and API limitations
Closed
#13 Partial-failure reporting and resume
Closed
#12 Configure the Gitea to GitHub push mirror (when GitHub is chosen)
Closed
#11 Create the Gitea repository, with AGPL license when GitHub is chosen
Closed
#10 Create the empty GitHub repository (optional)
Closed
#9 Preflight checks before any creation
Closed
#44 Read and validate PROJECT_LICENSE
Closed
#46 Document the key
Closed
#45 Apply the license on Gitea, independent of GitHub
Closed
#50 Test every license case
Closed
#51 Test the qc fetch and the command link
Closed
#47 Fetch the framework's own submodules
Closed
#48 Start through a command link
Closed
#49 Document the usage
Closed
#39 Test every case
Closed
#37 Keep every token out of everything else
Closed
#36 Create the new project's .env
Closed
#38 Document the feature and its risk
Closed
#35 Ask for a credential that .env does not provide
Closed
#29 Keep the confirmations interactive
Closed
#27 Read and validate the eight optional config keys
Closed
#31 Test every key and case
Closed
#30 Document the keys
Closed
#28 Use configured details instead of asking, and show their source
28 Issues created by 1 user
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
Opened
#35 Ask for a credential that .env does not provide
Opened
#36 Create the new project's .env
Opened
#37 Keep every token out of everything else
Opened
#38 Document the feature and its risk
Opened
#39 Test every case
Opened
#44 Read and validate PROJECT_LICENSE
Opened
#45 Apply the license on Gitea, independent of GitHub
Opened
#46 Document the key
Opened
#47 Fetch the framework's own submodules
Opened
#48 Start through a command link
Opened
#49 Document the usage
Opened
#50 Test every license case
Opened
#51 Test the qc fetch and the command link
Opened
#59 Add only the origin remote
Opened
#60 Describe the one remote in the README
Opened
#61 Test the single remote
Opened
#62 Bump the version to 0.3.1
Opened
#65 Update the analysis and design documents
Opened
#66 Add the Git excludes step
Opened
#67 Describe the excluded files in the README
Opened
#68 Test the excludes
Opened
#69 Bump the version to 0.3.2
Opened
#77 SSH key with a passphrase does not work