Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 380
    • Issues 380
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #880
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

Allow sync / fetch / push on bare repository

By telgl... on August 28, 2011 19:39 (imported from Google Code)


What steps will reproduce the problem?

  1. Clone into a bare repository, say xyz.git.
  2. In the xyz.git\config file, create a [remote "abc"] section with "url = ..." and "fetch = ..." and "push = ..." entries.
  3. Command-line "git fetch" or "git fetch abc" will now update this repo from the configured remote. Similarly "git push" etc. will send changes to the configured remote.

What is the expected output? What do you see instead?
(enhancement request): TGit should include an option to "fetch" into a bare repository from a configured remote, and to "push" from the bare repository into a configured remote. These could be similar to the "sync" options available for a working repository.

(current behavior): Right-click options for Tortoise Git on a bare repository do not include the option to sync. Tortoise Git treats the bare Git repo. just like a non-Git directory.

What version of the product are you using? On what operating system?
TGit 1.6.5.0, Win XP SP3

Please provide any additional information below.
One usage scenario (which I encounter regularly) where I would find this useful is when I use a USB stick to keep a repository up-to-date on a remotely located computer. To save space and writing time on the USB stick, its repo. is bare. However, updating the repo. on the USB stick from the master version on the server can't be done from the TGit interface. Similarly, any changes made in the working repository on the remote computer can be "pushed" through TGit to the USB stick, but then to get those into the master version on the server requires command-line tools.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking