ObliviOS Developer portal Project site

Home / Decisions / ADR-267

Apply the GitHub settings that wait for a public repository and read the public face of the project.

Accepted, recorded 18 November 2026.

Decision
ADR-267
Date
2026-11-18
Status
AcceptedAccepted (owner, 2026-11-18).
Mentions
ADR-262, ADR-265

1Decision

Apply the GitHub settings that wait for a public repository and read the public face of the project, as the owner allowed on 2026-11-18. (1) On all four repositories: secret scanning and push protection on, and the default branch protected against force-push and deletion (no review and no status check is required, so a normal push still works). (2) Read only: the public profile of the GitHub account, the live site page by page, and one capture of the home page in a browser.

2Why and evidence

A public repository is scanned for secrets at no cost, and its history was never offered to a scanner before; a protected default branch cannot be deleted or overwritten by a slip. The protection makes a rewrite of a history harder on purpose: ADR-265 names such a rewrite as an option, and it would need the protection lifted first.

3Consequences

Done and read on 2026-11-18 with gh api: secret_scanning and secret_scanning_push_protection are enabled on all four, the default branch of each is protected with force-pushes and deletions refused, and each has zero secret-scanning alerts (the scan may still be running).

Live site: the ten pages of the sitemap and a missing page answer 200 and 404, set no cookie, load nothing from another origin, hold no form, have a language, a title and one level-one heading, and have no image without text; the headers of ADR-262 are served; the 13 internal and 8 external links (the four repositories and their issue pages) answer 2xx; security.txt, robots.txt and the analytics script answer 200; a capture of the home page in the browser pane shows 11 requests, all to oblivios.org, and no console message.

Profile: a first name only, no biography, company, website, status or pinned repository, a location field that names a town, a public e-mail address that is the contact address, and four public repositories.

Not done: a capture of the other pages in a browser, an automated accessibility check and a phone viewport (V-4, W-5), the Speed Insights and preview settings of the host (W-3), whether the avatar is meant to be public, and whether the town in the profile is to stay (the owner decides; the agent changes no account setting).

4Review when

A scan alert appears; the protection blocks a change the owner wants (lift it for that change); the owner changes the profile.

Read from docs/governance/decision-log.md, entry ADR-267.