connecting atom/ on linux with GIT and github,

[dil_bert]

connecting  atom/ on linux with GIT and github,

dear experts - good day dear phpfreaks

 

today i have a question regarding connecting atom/ on linux with GIT and github,

ive heard that this would be but very simple from the command line and linux…

Set your email: https://help.github.com/articles/setting-your-commit-email-address-in-git/

After uploading keys, test your ssh connection: https://help.github.com/articles/testing-your-ssh-connection/

Switch repo to use ssh rather than https: https://help.github.com/articles/changing-a-remote-s-url/#switching-remote-urls-from-https-to-ssh

but if i look at my atom editor i have the options of

• connect with GIT
• connect with GITHub

well whats the difference here betweeen git and github!?

why cannot add some commits while i see the git with create detached commend - nothing happens here

[gizmola]

Git is a decentralized peer to peer VCS.  You start with git on your workstation and it is possible to use that without every sharing your code.  

Example:

• You create a project directory
• You add some files to it
• You initialize the directory as a git project using git init.
• You stage the files you have in your project using git add
• You commit these files to your git project using git commit

At that point you now have a local git repository, where you can create branches, continue to add files, do merges, commits etc.   Git will provide you the ability to see your history of changes, and compare versions of the project to prior versions to see what has changed.  You can tag a particular branch (version) of your project and in doing so use that as the basis for building or deployment of that code.

git was also designed so that people could share or duplicated code using git clone.  But it's important to keep in mind that you might just be sharing code with yourself, perhaps by using git clone to work on code on a 2nd machine.  Git was designed by Linus Torvald of Linux fame, to support the decentralized process he was using for work on the Linux code base, which was not based on a single centralized master server, and often required a lot of merging activity from lots of people who were often working in branches that then needed to be merged with other branches and so on.

Github saw that many projects did want a master repository, and also that it could be helpful to provide tools to facilitate the process of submitting changes that the core project leads might choose to accept or reject.  It's also nice to have a cloud based version of the code even for your own projects.  Github also adds project planning, bug tracking and documentation features that are nice for many projects to have, as well as configurable hooks that facilitate continuous integration.

Github essentially stepped into the same space occupied by sourceforge and other open source hosting sites in the days when subversion was the VCS favored by many open source projects.   As git gained traction and eventually won over the open source world, Github and other similar services like Bitbucket emerged and projects moved their source from subversion to git.  For newer projects git is a defacto standard for version control, so naturally github has continued to grow rapidly as more and more of the world's most important open source projects migrate to it.

Anyone can host source on github, so long as they make that source publically available.  If you want your repository to be private, you have to pay for that on a per user basis -- so Github is essentially now a giant "platform as a service" company that provides cloud based git repository hosting and open source project hosting.