5

Numerous posts make it clear that using a shared Dropbox folder as a git remote can lead to problems.

However, opinions seem more mixed about placing a local repository (e.g. cloned from Github) into a private Dropbox folder.

My question is twofold:

1) Is it dangerous to place a local repository in a private Dropbox folder (that syncs across multiple computers, all owned by me)?

2) Is my remote repo (on GitHub) in danger if a collaborator chooses to sync their local repository to Dropbox (i.e. a collaborator clones the repository to Dropbox and regularly commits and pushes)?

souzan
  • 289
  • 1
  • 2
  • 14
Jacob Socolar
  • 1,172
  • 1
  • 9
  • 23

1 Answers1

5

I prefer putting a git bundle (a compressed version of your Git repo, one you can clone) in a Dropbox folder.

Putting a full Git repo into Dropbox remains risky, as I mentioned here.

But should a collaborator do so, pushing to it would not influence the upstream GitHub repo, nor would it influence your own Dropbox-managed version of that repository.

souzan
  • 289
  • 1
  • 2
  • 14
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250