-
RepoFoundry 0.3.3
StableTirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 4sreleased this
2026-10-09 13:18:11 +02:00 | 10 commits to main since this releasecreate-project.sh --versionprintsRepoFoundry 0.3.3.Changed
- The
frameworksubmodule is bumped to v0.5.0, and.gitmodulesuses the lower-casesqa-qc-framework.gitURL.
Pull request: #75
Downloads
- The
-
RepoFoundry 0.3.2
StableTirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 3sreleased this
2026-10-08 08:34:23 +02:00 | 13 commits to main since this releasecreate-project.sh --versionprintsRepoFoundry 0.3.2.Changed
- The files the framework installs are excluded from git in the new project. After the templates are copied, the script adds
/.claude,/.agentsand/AGENTS.mdto the new project's.git/info/exclude, as its own step, "Git excludes" (MIL-009, PRs #70 to #74). No.gitignoreor tracked file changes and nothing is committed. The step is skipped when the framework steps are skipped, and a path git already tracks stays tracked and is named in the summary. - The README has a new section, "The files git ignores in the new project".
- The version is raised to 0.3.2.
Things to know
- The whole
.claudeand.agentsfolders are ignored, not only theirskillsfolders, so anything else kept there (settings, agents) is ignored too. - The entries live in
.git/info/exclude, which belongs to the clone. A fresh clone has neither the entries nor these files. Make the skills again withbash framework/scripts/install-skills.sh(aftergit submodule update --init --recursive).AGENTS.mdcannot be made again that way: it is a copy of a template that the project edits.
Upgrading
A project made by an earlier version is not changed. To get the same exclusions there, add the three lines
/.claude,/.agentsand/AGENTS.mdto its.git/info/excludeby hand. A file git already tracks stays tracked.Tests
The full suite passes: 1188 checks, 0 failed. The phase is described in
docs/milestones/mil-009-exclude-framework-files.mdand was reviewed in RC-032.Downloads
- The files the framework installs are excluded from git in the new project. After the templates are copied, the script adds
-
RepoFoundry 0.3.1
StableTirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 7sreleased this
2026-10-08 05:46:15 +02:00 | 30 commits to main since this releaseFirst tagged release of RepoFoundry (
create-project.sh --versionprintsRepoFoundry 0.3.1).Changed
- The local project has one remote,
origin(Gitea), with or without GitHub. A push tooriginreaches GitHub through the Gitea push mirror, so the script no longer adds agithubremote (MIL-008, PR #58). - The version is raised to 0.3.1.
Upgrading
A project made by an earlier version still has a
githubremote. The script leaves it alone; remove it withgit remote remove github. Nothing else needs to change.Also in this release
The version was not raised while the earlier phases were built, so 0.3.1 also carries them:
- project details preset in
config.env(MIL-004) - missing credentials asked, and the new project's own
.env(MIL-005) - the project license set in
config.env; AGPL-3.0 is the default only for a public GitHub project (MIL-006) - the framework's
qcchecklists fetched with it, starting through a command link, and the default configuration files (MIL-007)
Each phase is described in
docs/milestones/. The full suite passes: 1141 checks, 0 failed.Downloads
- The local project has one remote,