Skip to content
GitTree
Repositories

Open a bare repository

A bare repository has history but no working files, like the ones servers keep for others to push to (git init --bare, git clone --bare). GitTree opens it to show the graph, branches and tags, marks its tab bare, and turns off actions that need working files.

FreeUpdated

Works in GitTree Free: every local Git feature, once you are signed in.

On this page
  1. Before you start
  2. Where to find it
  3. Steps
  4. Expected result
  5. Create a bare repository
  6. If something goes wrong
  7. Questions
  8. Related

Before you start

  • A bare repository folder, usually named like project.git.

Where to find it

  • Open it like any repository: Open on the new tab, or Open Repository….
ActionmacOSWindows and Linux
Open Repository…⌘OCtrl+O

Steps

  1. Open the folder

    Choose Open and select the bare repository’s folder itself (the one with HEAD, refs and objects inside).

  2. Read its history

    The tab shows a bare badge. The graph, branches, tags and commit details work as usual.

  3. Know what is off

    Anything that changes working files, such as staging, committing or checking out, is unavailable, with the reason: A bare repository has no working files to change.

Expected result

You can browse and inspect a server-style repository without cloning it into a working copy.

Create a bare repository

In the Initialize a repository dialog, turn on Bare repository (history only, no working files) (create a repository). Keep it off for a project you work in.

If something goes wrong

I want to edit files in a bare repository

Clone it into a normal working copy (clone a repository) and push your commits back.

Questions

Can I push to a bare repository from GitTree?

Yes. Add its path or URL as a remote in your working copy and push to it, as you would to any server.