Main Branch Guard for GitHub Privacy Policy

Effective August 18, 2026 · Version 0.1.0

Main Branch Guard for GitHub has one purpose: on GitHub's web-based file editor, warn before you commit directly to a repository's default branch, and offer to switch to "Create a new branch and start a pull request" instead.

Data processed

The extension reads two things already present on GitHub's own file-editor page: the current branch name and the repository's default branch name, both already embedded by GitHub in the page's own data for the signed-in user, and which of GitHub's own "Commit directly" / "Create a new branch" options is selected in GitHub's own commit dialog. The extension does not request, decode, or infer anything beyond what is already on the page.

The extension does not read file contents, commit messages, diffs, account identity, cookies, or login state.

Storage, transmission, and sharing

All processing happens locally in the active browser tab. Main Branch Guard does not collect, transmit, sell, share, or retain the branch names, the selected commit option, file contents, or any other page data. It has no developer-operated server, analytics, advertising, account system, OAuth integration, network requests, or remote code.

What the warning does

When it detects a direct-commit submission targeting the repository's default branch, the extension shows a local on-page warning with two choices: "Create a branch instead," which selects GitHub's own "Create a new branch and start a pull request" option without submitting anything, or "Commit anyway," which resubmits the same commit GitHub was about to process. Both actions only use GitHub's own controls; the extension never commits, creates a branch, or opens a pull request on its own.

Site access

The extension runs only on github.com file-editor pages (URLs matching github.com/*/*/edit/*). It requests no other site access, no activeTab, and no background or storage permissions.

Retention and deletion

The extension keeps no database, history, or stored settings. Its only state is an in-memory flag that exists for a fraction of a second while it lets a user-confirmed "Commit anyway" click through, plus a cached read of the current page's branch names; nothing is written to disk. Closing the tab or navigating away discards everything.

Changes

If a future version changes how data is processed, this policy and Chrome Web Store disclosures will be updated before that version is distributed.

Contact

For privacy or support questions, use the developer contact address shown on the extension's Chrome Web Store listing.