You work with device A offline, push some commits to the bare repository in Google Drive folder, but because you are offline, those changes do not sync to the cloud. The cloud services have their own systems for merging conflicts, and that doesn't really work with git.
You can find some comparison information about different git hosting sites here.Īs people have pointed out (and as OP already knows), you can put the bare repository inside your local Google Drive/Dropbox folder and work with that, however, there are caveats. For example Bitbucket which offers some free private repositories. I would also suggest against Google drive/Dropbox based solutions, and go for a git hosting solution instead. Highlight the exact differences between two arbitrary commits/points in time.No, you can't.
Maintain a "development" branch that everybody works on, and a separate "release" branch which contains only completed features. Tag and return to specific revisions/points in time (we released version 1.0?)įorce all changes to be code-reviewed by somebody else before being added into the main branchĪutomatically reject a change if somebody tries to check in code that doesn't pass all your tests
Take a change person X made on Tuesday, a change you made today, ignore like 10-20 changes in between, replay them on top of each other, and create a new branch? Include a reason for each change, so that when you stumble across a bizarre piece of code, you can go back in time and determine whyĪllow hundreds of developers to collaborate at onceĪllow people to view the latest version of your project without giving them edit rights Specifically omit build files and user-specific settings from being includedīe able to view any change ever, or revert the entire project to a specific point in time.Īllow users to "branch" the project, make any arbitrary changes (without affecting other people!), then later merge it back in when everything is stabilized
0 kommentar(er)
