This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| cloneinto [2025/04/27 18:34] – created 202.164.130.88 | cloneinto [2025/06/19 17:59] (current) – admin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====Git Clone==== | + | ======Git Clone====== |
| - | Git Clone can only be invoked by those who are members of a repository. It will ask you for the //git// address (It will start with //git@...// ) Get that address from the owner of the repository. | + | Git Clone can only be invoked by those who are members of a repository. It will ask you for the //git// address (It will start with //git@...// ) Get that address from the owner of the repository. Cloning can only be done on the Work folder you had setup or one of the suitable sub-folders beneath that in the folder-tree. |
| For Git Clone to work, your private key //must be// available in the members sub-folder (inside the application folder) and the name of that file should be as explained below: | For Git Clone to work, your private key //must be// available in the members sub-folder (inside the application folder) and the name of that file should be as explained below: | ||
| Line 9: | Line 9: | ||
| The above is the //format// of the file. In the above, replace < | The above is the //format// of the file. In the above, replace < | ||
| - | For example; if the name of the repository is office_graphics and your name is Alpha then the filename inside the members sub-folder would be: | + | For example; if the name of the repository is **//office_graphics//** and your name is **//Alpha//** then the filename inside the members sub-folder would be: |
| // | // | ||
| Line 15: | Line 15: | ||
| There should NOT be any spelling mistake in the above filename. And the contents of the filename must be the private SSH key that was assigned to that member. Before the cloning action was done, the owner of the repository should have added that member and setup the keys for that member. So here, it is assumed that such a member already has the private key. | There should NOT be any spelling mistake in the above filename. And the contents of the filename must be the private SSH key that was assigned to that member. Before the cloning action was done, the owner of the repository should have added that member and setup the keys for that member. So here, it is assumed that such a member already has the private key. | ||
| + | ----- | ||
| + | [[/ | ||