GitHub Remote File Editor

Most repo edits, a typo in a README, a config value, one line of code, don't need a clone, a terminal, or an IDE. They need: open the file, change the text, commit. GitPad is built around that single loop, with nothing else in the way. Not a scaled-down IDE, and not trying to become one — the smallest possible interface between "I need to change this file" and "it's committed." The core design decision follows GitHub's own Contents API: file editability is a property of bytes, not filenames. Any file that decodes as valid UTF-8 is editable regardless of extension — an extension blocklist only greys out obviously-binary files as a UI hint, while the real gate is a strict UTF-8 decode of the actual bytes at open time, correctly handling both a text file with a misleading extension and a binary file with an innocent one. The system is a Next.js Server Actions architecture with zero client-side GitHub API calls: browser → Next.js → Server Actions → a single GitHubClient wrapper → GitHub REST API. Every write ties to the file's last-read SHA for optimistic concurrency, every server action independently re-validates owner/repo/branch/path/message/SHA regardless of what the UI already checked, and there is no persistence layer beyond an encrypted, server-only session cookie — GitHub itself is the only source of truth.