Book Image

Version Control with Git and GitHub

By : Alex Magana, Joseph Muli
Book Image

Version Control with Git and GitHub

By: Alex Magana, Joseph Muli

Overview of this book

<p>Introduction to Git and GitHub begins with setting up and configuring Git on your computer along with creating a repository and using it for exercises throughout the book. With the help of multiple activities, you’ll learn concepts that show various stages of a file—from when it is untracked to when it is set for tracking under version control. As you make your way through the chapters, you’ll learn to navigate through the history of a repository, fetch and deliver code to GitHub, and undo code changes. </p><p> </p><p>The first half of the book ends with you learning to work with branches, storing and retrieving changes temporarily, and merging the desired changes into a repository. </p><p> </p><p>In the second half, you’ll learn about forking as part of a collaborative workflow. You’ll also address modularity and duplication through submodules, tracing and rectifying faulty changes, and maintaining repositories. </p><p> </p><p>By the end of this book, you will have learned how to effectively deploy applications using GitHub.</p>
Table of Contents (8 chapters)

Git Archive

Apart from enabling release management through tagging, Git enables the packaging of source code as zipped and .tar files, making them available for downloads on release pages, and sometimes on download or installation pages. This is achieved through the git archive command.

Exercise 45: Packaging through GitHub Archive

To package source code using the git archive command.

  1. From your terminal, ensure that you are on the master branch and that it is even with origin, as shown in the following screenshot:
    Figure 6.43: Checkout of the master branch
  2. Run the git archive command with the arguments shown in the following screenshot:
Figure 6.44: Git archive

Note

The arguments are basically creating a compressed tarball for the abacus v1.0.0 release.

Outcome

Your path should now have the releases that can be uploaded or deployed to their respective pages, as shown in the following screenshot:

Figure 6...