Skip to content

docs: prepare the repository for public visibility - #23

Merged
danielededo merged 1 commit into
mainfrom
docs/prepare-public-repo
Oct 11, 2026
Merged

danielededo merged 1 commit into
mainfrom
docs/prepare-public-repo

Conversation

@danielededo

Copy link
Copy Markdown
Owner

Loose ends found while auditing the repo before making it public (history, files, issues and PRs had no secrets or personal data).

  • SECURITY.md: drop the template placeholders (<SECURITY_CONTACT_EMAIL>, [TO BE FILLED IN]); reports go through GitHub private vulnerability reporting only.
  • .github/ISSUE_TEMPLATE/config.yml: link the security policy from the issue chooser.
  • Remove scaffold leftovers: .github/CODEOWNERS (comments only), docs/README-TEMPLATE.md, docs/REPO-SETTINGS.md. README tree updated, and now lists docs/STORE-LISTING.md.
  • docs/STORE-LISTING.md: the repository becomes the website/support URL.

Deliberately left for after the switch: the private-repo cost note in safari.yml and AGENTS.md (editing the workflow triggers a macOS run, free only once public), and the README "not yet published on any store" status (until Edge approves).

Checks: npm run check (49 tests passed); issue template config parses.

@danielededo
danielededo merged commit 650b2e6 into main Oct 11, 2026
2 checks passed
@danielededo
danielededo deleted the docs/prepare-public-repo branch October 11, 2026 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant