{"id":23788,"date":"2023-05-10T04:15:17","date_gmt":"2023-05-10T04:15:17","guid":{"rendered":"https:\/\/www.booksofall.com\/es\/?post_type=product&p=23788"},"modified":"2023-05-10T04:15:52","modified_gmt":"2023-05-10T04:15:52","slug":"introduction-to-git-and-github","status":"publish","type":"product","link":"https:\/\/www.booksofall.com\/es\/introduction-to-git-and-github\/","title":{"rendered":"Introduction to git and github"},"content":{"rendered":"

Introduction to Git<\/span><\/h2>\n

Welcome to this Git and GitHub basics training guide! In this<\/span> Git crash course<\/span>, you <\/span>will learn the<\/span> basics of Git<\/span> so you can use Git to track your code<\/a> changes and <\/span>collaborate with other members of your team or open source<\/a> maintainers. <\/span><\/p>\n

Whether you are a newcomer to programming<\/a>, or an experienced one, you have to <\/span>know how to use Git. Most of the projects that a small or big group of developers work <\/span>on are done through GitHub or GitLab.<\/span><\/p>\n

It makes working with other developers so much more exciting and enjoyable, just by <\/span>creating a new branch, adding all your brilliant ideas to the code that can help the <\/span>project, committing it, and then pushing it to GitHub<\/a> or GitLab<\/a>. Then after the PR(pull <\/span>request) has been opened, reviewed, and then merged, you can get back to your code <\/span>and continue adding more awesome stuff. After pulling the changes from the <\/span>main\/master branch, of course. <\/span><\/p>\n

If what you just read doesn’t make any sense to you, don’t worry. Everything will be <\/span>explained in this eBook!<\/span><\/p>\n

This eBook will show you the basics of how to start using Git and try to help you get <\/span>more comfortable with it.<\/span><\/p>\n

It does look a bit scary in the beginning, but don’t worry. It’s not as frightening as it <\/span>seems, and hopefully, after reading this eBook, you can get a bit more comfortable with<\/span>
Git.<\/span><\/p>\n

Learning Git is essential for every programmer. Even some of the biggest companies <\/span>use GitHub for their projects. Remember that the more you use it, the more you’re <\/span>going to get used to it.<\/span><\/p>\n

Git<\/span> is without a doubt the most popular open-source version control system for tracking <\/span>changes in source code out there.<\/span><\/p>\n

The original author of git is<\/span> Linus Torvalds<\/span>, who is also the creator of<\/span> Linux<\/span><\/a>. <\/span><\/p>\n

Git is designed to help programmers coordinating work with each other. Its goals <\/span>include speed, data integrity, and support for distributed workflows.<\/span><\/p>\n

Version Control<\/span><\/h2>\n

Version control<\/span>, also called<\/span> Source control<\/span>, allows you to track and manage all of the <\/span>changes to your code. <\/span><\/p>\n

Why Use Version Control?<\/span><\/h4>\n
    \n
  • Multiple people could work on the same project simultaneously.<\/span><\/li>\n
  • Serves simultaneously as a repository, project narrative, communication medium, <\/span>and team and product management tool.<\/span><\/li>\n
  • Records all changes in a log <\/span><\/li>\n
  • Allows team members to work concurrently and provides the facility to merge <\/span>that work back together.<\/span><\/li>\n
  • Traces each change made to the software.<\/span><\/li>\n
  • Data is transitory and can be lost easily.<\/span><\/li>\n<\/ul>\n

    What is Version Control System?<\/span><\/h4>\n

    Also known as a source code manager (SCM) or a revision control system (RCS), it is a <\/span>system that keeps track of changes to a file or set of files and in case of any problems, <\/span>lets you go back in history, comparing changes over time, and easily revert to a <\/span>working state of your source code. SVN, Mercurial, and the massively popular Git are <\/span>popular version control systems for developers. All of these are free and open-source.<\/span><\/p>\n

    \"\"<\/p>\n

    With distributed version control systems like Git, you would have your source code <\/span>stored on a remote repository like GitHub and also a local repository stored on your <\/span>computer.<\/span><\/p>\n

    You will learn more about remote and local repositories in the next few chapters. Still, <\/span>one of the main points for the moment is that your source code would be stored on a <\/span>remote repository, so in case that something goes wrong with your laptop, you would <\/span>not lose all of your changes, but they will be safely stored on GitHub<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"