Hi Ken,
> Le 27 janv. 2018 à 15:38, kmo <[email protected]> a écrit :
>
> I don't understand how iceberg handles resource files that you might also
> like to version along with the pharo code.
For now, Iceberg do not really handle these files but it is planned in a next
future.
> Say I have an CSV file and a text file that my pharo application uses. How
> do I include these in the iceberg commit/push? How do I see changes made in
> these files from version to version?
Currently, you cannot do anything related to this through the UI.
What you could do is to call directly Iceberg API to commit ressources to the
git repository:
1/ write the resource content in git working copy (std file system). There is a
utility method: IceRepository>>#saveContent: aString inWorkingCopyFile:
aRelativePathString
2/ add these files to git index through: IceRepository>>addFilesToIndex:
aListOfPaths
3/ commit :
iceRepository
commitIndexWithMessage: commitMessage
andParents: { iceRepository headCommit }
You can also read ressources by suing IceRepository>>#contentOfFileNamed:
aPathString commit: aCommitId
Christophe.
> Does iceberg only handle pharo code? Generally git clients don't care about
> the file type - and it it is any kind of text you can see the actual
> differences between each commit.
>
> Ken
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>
