Hi Luc, most of these problems are solved by gitfiletree by Goubier Thierry. It automatically commits the thing that you commit with Monticello, it allows you to push, and it shows you the history (sometimes a bit screwed, but good enough). ConfigurationOf works with GitHub projects, but I think there is also something in a new Metacello that I don’t know about.
Big con is that you essentially communicate with git through Monticello. And to doing advanced stuff, like a lot of branching, pull requests and so on, gives an impression that you are always hacking something. If you want to really work with git, you want to be able to have only git versions of your code, stage and commit certain changes, communicate with remote repos, and if something goes wrong talk to command line and deal with file-based pharo representation. But instead of this you have one more screen of Monticello + nasty metadata which complicates merging. Uko > On 02 Dec 2014, at 17:00, Luc Fabresse <[email protected]> wrote: > > Hi, > > I continue the discussion here because I really would like to know the cons > of using Git + Pharo. > From kilon's video (thx) and the discussion that followed, I have the > following questions about possible drawbacks of Git+Pharo: > > - The most important point to me is: does ConfigurationOf work correctly with > a repo on GitHub for example? any example somewhere? > > - we should go to command line to commit/update but that could be saved with > what has been done by Dale in tODE (shell integration, UI to commit, > push/pull) IIUC. right? > > - Merging could be harder because it would rely on git tools? > > - opening a filetree repo in MC does not show the latest content since it is > the local git repo that may not be in sync with the remote one => you should > first pull the repo > > Thx for enlightening me, > > #Luc
