I work on a project that uses smalltalk as a part of a larger system. We version control most of the code (Objective-C, mainly) using Git. Currently the repo has a build script under version control which specifies the monticello package versions to fetch for a given commit. This works okay, and keeps everything in step, but the change histories are in two places (Git and monticello) which is undesirable, and branching/merging is difficult. I'm looking at using filetree (https://github.com/dalehenrich/filetree) to store the smalltalk source in the git repo. I was wondering what the workflow is within the image. Is there an easy way to keep the code on the filesystem in sync with the code in the image? At the moment it seems that there will be a lot of loading/saving in the monticello browser whenever I change code either using git or within the image. For example, do I have to save code out to the filesystem using the Monticello browser, and then inspect the diffs in git? -- View this message in context: http://forum.world.st/Git-filetree-workflow-tp4701465.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.