PrettyBaby's first GitHub OAuth path proved that a development connection and encrypted token persistence could work. It also exposed a problem: a broad user OAuth token was not a suitable default for production repository writes.
The architecture changed course. The preferred model became a GitHub App installed on repositories the user selects, with short-lived installation tokens and an explicit repository choice before any future write. All-repository installation and unnecessary administration, actions, secrets, or workflow permissions were excluded from the initial plan.
The implemented installation flow lets an authenticated project owner begin installation. Its callback validates signed state, retrieves installation and selected-repository metadata through a server-only API boundary, and stores curated owner-scoped records. The short-lived installation token used for discovery is not persisted or returned to the browser.
No repository write exists yet. PrettyBaby cannot connect a project to a selected destination, push files, create commits or branches, or open a pull request. The milestone narrows authority before adding convenience.
← Back to PrettyBaby