Features in depth

Publishing is opt-in at the level of an individual path. There is no "publish this folder and hope". The set of published paths is stored with the link, and any request for a path outside that set is refused — it is not merely hidden from a listing.

Stylesheets, images, fonts and scripts referenced by your published pages are served alongside them, and relative links between published files are rewritten so they resolve under the shared link. Interactive reports — coverage explorers with per-file drill-down, notebook exports, dashboards built from a static bundle — keep their behaviour instead of degrading to unstyled markup.

You nominate the page the link should open. Recipients land on the document itself, which matters when you paste the link into a client email or a ticket and want zero navigation.

A snapshot is a frozen copy of the selected files. Nothing you push afterwards changes what viewers see until you explicitly update the snapshot. This removes the most common accidental-exposure risk in ad-hoc publishing: a later commit silently changing, or expanding, what is public.

A link can be left open to anyone, or restricted to an explicit list of email addresses, or to entire domains — useful for "anyone at the client" without collecting every individual address. Restricted links verify viewer identity before serving any file, including individual assets requested directly.

Published URLs carry a random suffix, are never listed in the sitemap, and are not browsable from the homepage. Search engines are pointed at the marketing and policy pages only.

Each link records its views so you can see whether the person you sent it to actually opened it, and spot access you did not expect. The log lives in your dashboard next to the link.

One toggle stops serving a link immediately. No deploy, no DNS wait, no cache purge ceremony. You can re-enable it later without changing the URL.

Recipients who sign in can keep the links shared with them in one place, which is handy when a client or auditor receives several reports over time.

If your account can see many organizations, you choose which owners to sync. The repository picker then stays short, and GitSnap only enumerates what you asked it to.

Snapshots are screened for credential-harvesting and phishing patterns, and publishing is rate-limited per account. This keeps the service — and therefore your links' reputation with corporate web filters — clean.