Menu

Stage 11

Day 3 — The repository is public

The ELVN source history is public, verified and separated from the production deployment process.

CompletedDay 3

Repository

The ELVN source code is now public at github.com/elvn11ask/elvn.

The first 12 published commits were preserved exactly as they were created. Release v0.1.0 records the initial public launch, and the website now links directly to the repository.

No history was rewritten, squashed or force-pushed.

Verification

The published Git history and release were checked for credentials, private keys, local paths and wallet recovery material. No secrets were found.

CI now verifies the lockfile install, dependency audit, secret scan, linting, TypeScript, tests, production build, SEO checks and a restricted source artifact.

CI does not deploy the production website. Production remains a separate server-side process and GitHub does not currently hold the VPS credentials.

Cleanup

A batch of 72 local files with the suffix 2 was investigated before removal.

Seventy were exact byte-for-byte copies. Two were older copies created before a verified GitHub URL fix and its regression test. They contained no useful changes. Every canonical file was preserved, and no duplicate entered the repository or production build.

The repository is public without pretending that publication itself is product progress. It is now a verifiable part of the public record.

Decisions

  • Keep the published Git history intact
  • Require CI checks without giving GitHub Actions production credentials
  • Keep production deployment separate until a dedicated secrets review

Rejected or deferred

  • Rewriting or condensing the existing commit history
  • Presenting GitHub Actions as the production deployment mechanism

Materials

  • Public repository and release v0.1.0
  • CI, dependency and secret checks
  • Duplicate-file audit