How GitSnap works

You create a GitSnap account and then authorize GitHub through GitHub's own OAuth consent screen. GitSnap never asks for your GitHub password, and the authorization can be revoked from your GitSnap dashboard or from GitHub's applications settings at any time.

The authorization is used for two things only: listing the repositories you can access, and reading the specific files you choose to publish.

Your dashboard lists the repositories available to your account, private ones included. If you belong to several organizations, you can choose which owners to sync so the list stays short and relevant instead of showing hundreds of repositories.

You browse the repository tree and tick the individual files that should be public. Everything you do not tick is never copied and never reachable through the published link. This is the core of the model: selection is explicit and opt-in, per file.

You also choose an entry file — the page the link opens directly, so a recipient lands on the report itself rather than on a file listing.

GitSnap copies a snapshot of the selected files and serves them at an unlisted URL with a random suffix. The recipient needs no GitHub account and no GitSnap account. Relative links, stylesheets, images and scripts between the published files keep working, so multi-file reports render the way they do locally.

Optionally, you can restrict a link to specific email addresses or to whole company domains. Restricted links require the viewer to prove their identity before any file is served.

Snapshots are immutable on purpose. A published link keeps showing exactly the content you published, even if the branch moves, history is rewritten or the repository is deleted. Nothing you push later leaks out automatically.

When you want viewers to see newer content, you press Update snapshot in the dashboard. GitSnap re-reads the same selected paths at their current state and replaces the snapshot behind the same link, so the URL you already shared stays valid.

Every published link has an instant off switch in the dashboard. Switching it off stops serving the files immediately, including direct requests for individual assets, and returns a plain notice instead. You can switch it back on later.