Hi Fran�ois,
with gitfiletree://, there isn't any real place describing a multi-developper workflow because it is designed to work along existing workflows... as much as possible.
In short, you work like you used to do in git, and gitfiletree ensures that the commit are properly made, that you have access to your development history (your true development history: the git one), and that pushes and pulls are made as painless as possible.
After, you just manage your git the way you like it. Branches, merging, one branch per developper, whatever: gitfiletree:// will ensure that what you see inside Pharo is what you have done in git, and that what you do in Pharo is properly committed to git.
Now, the bad thing: git merge conflicts :( When merging packages under git, some files will regularly(allways :() conflict: the version history of the package and the method properties. Whatever way you resolve those conflicts, gitfiletree:// will cope because
it never reads them, but, still, having conflicts in git isn't cool.
We have a better integration coming, through Max Leske work on integrating libgit to Pharo, and we will be able to solve some of the issues above ;)
Thierry
De : Pharo-dev [pharo-dev-bounces@lists.pharo.org] de la part de Fran�ois Stephany [tulipe.moutarde@gmail.com]
Envoy� : samedi 26 avril 2014 19:06
� : Pharo Development List
Objet : Re: [Pharo-dev] Fast way to load package form github
I'm a bit lost of what is currently possible to do with git in Pharo. Is there a place where you describe your workflow in a multi-developer environment?
We currently use git flow[1] for our iOS, Android and Rails apps. We would love to use the same for Pharo. What we are doing now is using a filetree repository under a src/ directory sitting next to the image. We use versionner to save all our packages in the
filetree tree and then we `git commit/push`.
It was working fine while I was alone but we are now two developers working on this and I do not feel confident about this flow; merging filetree tree in CLI doesn't sound like a good idea. probably not be practical.
The second developer is working on this since yesterday so we haven't yet decided how we gonna handle this.
I would love to hear from people working with git and Pharo.