Hi Phil,
with FileTree, you need to either create the git repository on the
command line with:
$ git init
or clone your remote hosted repository with:
$ git clone <whatever the address of your repository is>
then, inside the git created folder you create whatever structure you
want and save the package there (with the right filetree:// repository).
Then you commit, with git commit, to make sure your package version is
recorded by git. A save of the package with FileTree will overwrite the
previous one and erase all traces of the history (apart from the version
history in the package itself, but this one is totally useless with
filetree).
If you want a better git integration, use gitfiletree:// instead of
filetree://. Then saving the package will do a commit on the repository
with the right comment (i.e. your package version comment will be the
commit message) and all the packages versions will be visible when you
open the gitfiletree repository (and the versions will be the git
recorded data). That is, with gitfiletree your repository will look and
behave as if it was a normal mcz repo.
Regards,
Thierry
Le 02/10/2013 09:19, [email protected] a écrit :
I have been loading Filetree in a fresh image, created a sample package,
a sample class, a sample method.
The created a MCPackage and saved it into a filetree repository (which
happens to be a folder on the machine, no problem).
Now, how is one associating that with git? (and github or bitbucket).
Should I do a normal git thing, creating the project etc from the
command line (or using SourceTree, which happens to lower my level of
Git headaches).
Thanks for outlining the process.
I need private repos and as we do use Atlassian
Bitbucket/Jira/Confluence for the project, Filetree + Git is a great
answer I'd like to have working.
Thx!
Phil
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95