• v0.3.3 43ce34267e

    RepoFoundry 0.3.3
    TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 4s
    Stable

    Tirsvad released this 2026-10-09 13:18:11 +02:00 | 10 commits to main since this release

    create-project.sh --version prints RepoFoundry 0.3.3.

    Changed

    • The framework submodule is bumped to v0.5.0, and .gitmodules uses the lower-case sqa-qc-framework.git URL.

    Pull request: #75

    Downloads
  • v0.3.2 3e0047f36f

    RepoFoundry 0.3.2
    TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 3s
    Stable

    Tirsvad released this 2026-10-08 08:34:23 +02:00 | 13 commits to main since this release

    create-project.sh --version prints RepoFoundry 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, /.agents and /AGENTS.md to the new project's .git/info/exclude, as its own step, "Git excludes" (MIL-009, PRs #70 to #74). No .gitignore or 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 .claude and .agents folders are ignored, not only their skills folders, 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 with bash framework/scripts/install-skills.sh (after git submodule update --init --recursive). AGENTS.md cannot 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, /.agents and /AGENTS.md to its .git/info/exclude by 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.md and was reviewed in RC-032.

    Downloads
  • v0.3.1 b90050e6c4

    RepoFoundry 0.3.1
    TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 7s
    Stable

    Tirsvad released this 2026-10-08 05:46:15 +02:00 | 30 commits to main since this release

    First tagged release of RepoFoundry (create-project.sh --version prints RepoFoundry 0.3.1).

    Changed

    • The local project has one remote, origin (Gitea), with or without GitHub. A push to origin reaches GitHub through the Gitea push mirror, so the script no longer adds a github remote (MIL-008, PR #58).
    • The version is raised to 0.3.1.

    Upgrading

    A project made by an earlier version still has a github remote. The script leaves it alone; remove it with git 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 qc checklists 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