Create the repository
Create a public repository named bmitdee-js under the GitHub account or organization you control. Do not initialize it with another README if you will upload this prepared repository.
Repository publication guide
The complete repository ZIP is ready. These steps keep production secrets out, enable tests and Pages, and connect the public developer hub after the repository exists.
bmitdee-js/
├── packages/core
├── packages/adaptive
├── packages/elements
├── packages/cli
├── test-vectors
├── methodology
├── examples
└── .github/workflowsCreate a public repository named bmitdee-js under the GitHub account or organization you control. Do not initialize it with another README if you will upload this prepared repository.
Confirm the ZIP contains packages, tests, methodology, examples and workflows—and contains no config/db.php, credentials, user data or server logs.
git init git add . git commit -m "Initial BMITDEE JS platform release" git branch -M main git remote add origin YOUR_REPOSITORY_URL git push -u origin main
In repository Settings → Pages, choose GitHub Actions. The included workflow validates the project and deploys the playground app.
The workflows use read-only contents permission for tests and Pages-specific permissions for deployment. The release workflow writes release assets only when a version tag is pushed.
git tag v0.1.0 git push origin v0.1.0
The included release workflow creates a downloadable source asset and release notes.
Edit /developers/config.js on the production site and set repositoryUrl and githubPagesUrl. The hidden “View on GitHub” controls will then appear without changing every page.
ads.txt file—which is not part of this code repository.npm run check.npm run typecheck.bmitdee-js ZIP to GitHub.