"Metadata" : "false"to project root’s
- commit the change
- in every image with the repo: open Monticello Browser, right click on the repository and select
Flush cached versions
version & co.files will be automatically removed when you make a change in the package
GitFileTree now has a metadata-less mode that finally gets rid of those pesky
version & co. files that caused merge conflicts more than they should. Plus all the metadata is stored much more accurately by git itself (yay, no more broken ancestry).
To get rid of it, you need to add
"Metadata": "false" to your
.filetree file in the repository root. Note the double quotes in
"false" — it’s a string, not boolean. The file should look something like this.
Now commit the change and you should be done… or not.
Pharo caches all those properties, so in every image where you’ve added the repository, you need to open the Monticello Browser, right click on the incriminating package and select
Flush cached versions for it to load the modified properties.
Doing the steps above will not get rid of the metadata files, you can either remove them manually, or just let them be — once you make any code change and commit it in Pharo, the metadata (for the given package) will be automatically removed, so you don’t need to worry about them.
Finally, if you want to be fancy, you can do all the above directly from Pharo.