Trying to understand GitHub (local and online)

[Russ Winter]

Folks,

I am slowly trying to understand GitHub... any help would be appreciated...

OK, first up, I obviously have a http environment setup, with a /docroot/ folder, where the web-server has access. Should I have a two folders? One for the GitHub repo's to be stored, not accessible by the web-process and then a separate folder ( the /dcoroot/ ) where I would then copy to, for testing under the web environment.  IE: gitHub repo storage is unique and a separate folder structure to the actual testing/web environment folder structure. Or should they be combined,  eg: the web test and repo folder structures, are the same tree?

What is the difference between a "Fork" and a "Clone"? 

I have guessed I need to "Clone" the platform & cms projects to my own machine to get a copy, and I am guessing that I have to manually "sync" each repo when I want to refresh it to the latest stored versions on gitHub to keep up to date with changes? 

Without getting in to "phing" and automation (yet)...  If I want to test or play with an installed version of the platform or cms, I guess I would manually copy the "file-set" from the appropriate repo folder on my machine to another folder and install as per normal? but this new copy will now have no relationship with the original cloned copy/repo? and any changes made in the newly installed copy would need to be manually reflected in the original clone before I could generate any form of patch for submission back to the original project? (I have yet to work out how to do that, but at the moment am just trying to work out how to correctly setup GitHub on my own machine)

If I was to want to build my own component say. On my own machine, I would make a new folder, add that to my own local GitHub repo's.

I see I have two choices..

    a) I can add a new repo to my own "local" (seen in "Your Computer", on the GitHub Mac GUI)

    b) I can add a new repo to my GitHub repo's (seen in "GitHub > RussW", on the GitHub Mac GUI)

If I only add a repo to my local computer (option A) and then copy files in to the repo folder, these are seen as "Uncommitted Changes" and I still have the option (as this is a change to the repo) to "Commit & Sync", does this commit and sync push to GitHub, or simply commit the changes to my own local repo metadata?

What I am not understanding is the difference/relationship between the "Local" and "Online" options of GitHub. What I am trying to achieve is to work on some stuff just on my own local computer, and not push a repo up to GitHub yet, but still maintain the commit history. If that makes sense...

thanks for your assistance and advice folks, 

Russ

[Mark Dexter]

I have the .git folder off the root folder of the joomla instance (in other words, at the same level as administrator).

A fork is a github term for a special kind of clone. A clone is just a copy of any other repo. A fork for Github is a clone that has a relationship with a remote repo. For example, when you create a fork of joomla-cms it creates a remote called "upstream". This makes it easy (but not automatic) to keep your fork up to date with changes in the upstream repo.

There is a very basic tutorial here: http://docs.joomla.org/index.php?title=Git_for_Testers_and_Trackers. Once you get the basics, it's not too hard to fill in the rest. But there definitely is a learning curve.

Would it be helpful to have a webinar about git for testers and coders?

Mark

Russ

--
You received this message because you are subscribed to the Google Groups "Joomla! General Development" group.
To post to this group, send an email to joomla-de...@googlegroups.com.
To unsubscribe from this group, send email to joomla-dev-gene...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/joomla-dev-general?hl=en-GB.

[Nick Savov]

+1 on the webinar :)

Kind regards,
Nick

>> What is the difference between a "*Fork*" and a "*Clone*"?
>>
>> I have guessed I need to "*Clone*" the platform & cms projects to my own

>> in to the repo folder, these are seen as "*Uncommitted Changes*" and I
>> still have the option (as this is a change to the repo) to "*Commit &
>> Sync
>> *", does this commit and sync push to GitHub, or simply commit the

[brian teeman]

Thanks for the docs - going to try them out in the next few days  and yes please to the webinar 

>> joomla-dev-general@googlegroups.com.

>> To unsubscribe from this group, send email to

>> joomla-dev-general+unsub...@googlegroups.com.

>> For more options, visit this group at
>> http://groups.google.com/group/joomla-dev-general?hl=en-GB.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! General Development" group.
> To post to this group, send an email to

> joomla-dev-general@googlegroups.com.

> To unsubscribe from this group, send email to

> joomla-dev-general+unsub...@googlegroups.com.

[Matt Thomas]

I did a basic Git webinar for the GSoC students earlier this year. I'm fairly certain it was recorded, but I don't where it is available. I can check with the GSoC admins to see if we can post it somewhere if anyone is interested.

Best,

Matt

Sent from my phone that uses an open source operating system.

To view this discussion on the web, visit https://groups.google.com/d/msg/joomla-dev-general/-/yJPyfo3P6BoJ.
To post to this group, send an email to joomla-de...@googlegroups.com.
To unsubscribe from this group, send email to joomla-dev-gene...@googlegroups.com.

[Matt Thomas]

I also *highly* recommend anyone new to Git to use it via a command line interface, before using a WYSIWYG, so that you get familiar with how Git works. The basics are not that hard and it is a great way to understand Git.

Best,

Matt

Sent from my phone that uses an open source operating system.

[Mark Dexter]

That would be great to post that on Youtube or somewhere. Mark