Understanding the basics of Git and GitHub [closed]

by

  1. What is the difference between Git and GitHub?

    Git is a version control system; think of it as a series of snapshots (commits) of your code. You see a path of these snapshots, in which order they where created. You can make branches to experiment and come back to snapshots you took.

    GitHub, is a web-page on which you can publish your Git repositories and collaborate with other people.

  2. Is Git saving every repository locally (in the user’s machine) and in GitHub?

    No, it’s only local. You can decide to push (publish) some branches on GitHub.

  3. Can you use Git without GitHub? If yes, what would be the benefit for using GitHub?

    Yes, Git runs local if you don’t use GitHub. An alternative to using GitHub could be running Git on files hosted on Dropbox, but GitHub is a more streamlined service as it was made especially for Git.

  4. How does Git compare to a backup system such as Time Machine?

    It’s a different thing, Git lets you track changes and your development process. If you use Git with GitHub, it becomes effectively a backup. However usually you would not push all the time to GitHub, at which point you do not have a full backup if things go wrong.
    I use git in a folder that is synchronized with Dropbox.

  5. Is this a manual process, in other words if you don’t commit you won’t have a new version of the changes made?

    Yes, committing and pushing are both manual.

  6. If are not collaborating and you are already using a backup system why would you use Git?

    • If you encounter an error between commits you can use the command git diff to see the differences between the current code and the last working commit, helping you to locate your error.

    • You can also just go back to the last working commit.

    • If you want to try a change, but are not sure that it will work. You create a branch to test you code change. If it works fine, you merge it to the main branch. If it does not you just throw the branch away and go back to the main branch.

    • You did some debugging. Before you commit you always look at the changes from the last commit. You see your debug print statement that you forgot to delete.

Make sure you check gitimmersion.com.

More Related Contents:

  1. Multiple GitHub accounts on the same computer?
  2. git command for making one branch like another
  3. How can I delete all Git branches which have been merged?
  4. GitHub folders have a white arrow on them
  5. “fatal: Authentication failed for” when pushing to GitHub from Visual Studio Code (1.62.2)
  6. How to remove a directory from git repository?
  7. Remove folder and its contents from git/GitHub’s history
  8. Preferred Github workflow for updating a pull request after code review
  9. git gc –aggressive vs git repack
  10. Github remote permission denied
  11. Clone only one branch [duplicate]
  12. Github Push Error: RPC failed; result=22, HTTP code = 413
  13. Remote origin already exists on ‘git push’ to a new repository
  14. How to link to specific line number on github
  15. Can you issue pull requests from the command line on GitHub?
  16. Git lfs – “this exceeds GitHub’s file size limit of 100.00 MB”
  17. Clone A Private Repository (Github)
  18. Merge changes from remote github repository to your local repository
  19. How are commits counted by the GitHub contributions graph?
  20. github/git Checkout Returns ‘error: invalid path’ on Windows
  21. git 2.32 git push -u origin master Nothing happens
  22. How can I rollback a git repository to a specific commit?
  23. I can’t delete a remote master branch on git
  24. Why doesn’t git recognize that my file has been changed, therefore git add not working
  25. How to keep different content of one file in my local and github repository?
  26. How to commit a change with both “message” and “description” from the command line? [duplicate]
  27. GitHub – HTTPS access
  28. Can I update a forked project, on git, to the original/master copy?
  29. Adding self-signed SSL certificate without disabling authority-signed ones
  30. Jenkins-Build when a change is pushed to GitHub option is not working

Leave a Comment