Learning Path: End-to-End Git

Learning Git 14 lectures 01:15:17 Learning Git - The Course Overview Get introduced to Git and learn how it can help developers work more efficiently.

• What Git is
• Learn about the different features that Git has to offer

Git Version Control Version control is very important to track changes when several people are working on a single project.

• What version control is
• How Git approaches version control
• Advantages of distributed version control

Choosing a Workflow Different team dynamics requires different collaboration techniques. Choose the workflow that suits your group.

• Choose the familiarity of a centralized workflow while capitalizing on Git's additional advantages
• Create feature branches to keep new development from interfering with the stable code base
• Use the open source forking model to allow collaborators from anywhere while keeping your main repo protected

Initialization Collaboration on changing content necessitates the ability to keep a history of modifications. Initialize your Git repository right away to begin tracking changes.

• Use "git init" to create files that turn your project directory into a real-life repository with full history capability
• Create new, untracked files and see how Git reports them as they move from the working directory to the staging area
• View a comparison between the staging area and the tip of your current branch to see what will be committed

The First Commit After making changes, your project is in a working state, which you need to save before further modifications. Use "git commit" to check in this set of changes.

• Make changes to files in the working directory and view the comparison to the staging area
• Stage all files and compare them with your most recent commit
• Commit the changes with the "git commit" command, supplying a message indicating why the changes were made

Managing the Remotes In order to collaborate, other team members need access to your repository. Add a link to an online remote repository where everyone's changes will be gathered.

• Create a remote repository on GitHub and link to your local repository, or clone an existing GitHub repository, and get the remote automatically established
• Securely push changes from your local repository to any linked remote
• Use key-based SSH authentication to push changes to your remote

Viewing the History You need to be able to identify when changes were made to files and who made them. Use "git log" with various options to see the story of how your project was built.

• Use "git log" with formatting options to see the entire history of your branch, displaying information that's relevant to you
• Narrow your focus to the history of a single file, or to commits falling within a given range of time or between two references
• Check out commit hashes or references to time-travel to the state of the project when the commit was made

Branching and Forking Keep your work streams clean and isolated. Make branches for each feature and let team members work with copies of the original repository.

• Create a new local branch for your new feature and push to your remote
• Create a fork from the upstream branch and work from a local clone of that fork
• Add a remote link to the original repository to track upstream changes

Synchronizing Keep current with updates from other team members. Track and pull down updates from shared branches.

• Specify a remote tracking branch
• Pull remote changes into your local branch with a merge
• Get updates with the rebase feature when you have local commits

Issuing Pull Requests Submission of work requires an approval process. Use a pull request as a means to discuss and approve reviewable changes.

• Push changes to your fork and use GitHub to issue a pull request to the upstream
• Rebase and resolve merge conflicts when other team members modify the same code before your submission is merged
• Use a graph to visualize the history of your merged feature with respect to other branches

Interactive Rebasing Small commits can cause noisy history and difficult conflict resolution. Use interactive rebasing to squash a range of commits into one.

• Use an interactive rebasing tool to view all unpushed commits
• Squash all commits except the first one so that all changes are condensed into one commit
• With your commits squashed, rebase against the upstream and resolve conflicts, if any

Tagging a Release You want to keep track of specific versions of your project, such as those used in deployments. Use the tagging feature to permanently mark any point in the project's history.

• In your local repository, check out the commit that will be deployed
• Use the Git tag command to create a named reference to the checked-out commit
• Push your tag upstream, where it can be referenced at any point in the future

Tracing Code When collaborating, you need a quick insight into who added or removed code and why. Use the blame feature in forward and reverse order to discover where changes originated from.

• Navigate the repository history to locate a line of code that you need more information about
• Use the Git blame command to see the last person to touch that line of code at that point in history
• If the code has been deleted, use Git blame in the reverse direction to locate the last commit where the line appeared

Where to Go Next? You've acquired substantial knowledge on a powerful versioning tool. Review the lessons learned and get some hands-on experience.

• Review the abstract concepts covered, noting the advantages afforded by distributed version control
• Recall the techniques learned for synchronization and the ways in which choosing different workflows and using distributed control guides our approach to collaboration
• Become well-versed in Git as you contribute to open source projects and create your very own

Learning Git. 14 lectures 01:15:17 Learning Git - The Course Overview Get introduced to Git and learn how it can help developers work more efficiently.

• What Git is
• Learn about the different features that Git has to offer

Git Version Control Version control is very important to track changes when several people are working on a single project.

• What version control is
• How Git approaches version control
• Advantages of distributed version control

Choosing a Workflow Different team dynamics requires different collaboration techniques. Choose the workflow that suits your group.

• Choose the familiarity of a centralized workflow while capitalizing on Git's additional advantages
• Create feature branches to keep new development from interfering with the stable code base
• Use the open source forking model to allow collaborators from anywhere while keeping your main repo protected

Initialization Collaboration on changing content necessitates the ability to keep a history of modifications. Initialize your Git repository right away to begin tracking changes.

• Use "git init" to create files that turn your project directory into a real-life repository with full history capability
• Create new, untracked files and see how Git reports them as they move from the working directory to the staging area
• View a comparison between the staging area and the tip of your current branch to see what will be committed

The First Commit After making changes, your project is in a working state, which you need to save before further modifications. Use "git commit" to check in this set of changes.

• Make changes to files in the working directory and view the comparison to the staging area
• Stage all files and compare them with your most recent commit
• Commit the changes with the "git commit" command, supplying a message indicating why the changes were made

Managing the Remotes In order to collaborate, other team members need access to your repository. Add a link to an online remote repository where everyone's changes will be gathered.

• Create a remote repository on GitHub and link to your local repository, or clone an existing GitHub repository, and get the remote automatically established
• Securely push changes from your local repository to any linked remote
• Use key-based SSH authentication to push changes to your remote

Viewing the History You need to be able to identify when changes were made to files and who made them. Use "git log" with various options to see the story of how your project was built.

• Use "git log" with formatting options to see the entire history of your branch, displaying information that's relevant to you
• Narrow your focus to the history of a single file, or to commits falling within a given range of time or between two references
• Check out commit hashes or references to time-travel to the state of the project when the commit was made

Branching and Forking Keep your work streams clean and isolated. Make branches for each feature and let team members work with copies of the original repository.

• Create a new local branch for your new feature and push to your remote
• Create a fork from the upstream branch and work from a local clone of that fork
• Add a remote link to the original repository to track upstream changes

Synchronizing Keep current with updates from other team members. Track and pull down updates from shared branches.

• Specify a remote tracking branch
• Pull remote changes into your local branch with a merge
• Get updates with the rebase feature when you have local commits

Issuing Pull Requests Submission of work requires an approval process. Use a pull request as a means to discuss and approve reviewable changes.

• Push changes to your fork and use GitHub to issue a pull request to the upstream
• Rebase and resolve merge conflicts when other team members modify the same code before your submission is merged
• Use a graph to visualize the history of your merged feature with respect to other branches

Interactive Rebasing Small commits can cause noisy history and difficult conflict resolution. Use interactive rebasing to squash a range of commits into one.

• Use an interactive rebasing tool to view all unpushed commits
• Squash all commits except the first one so that all changes are condensed into one commit
• With your commits squashed, rebase against the upstream and resolve conflicts, if any

Tagging a Release You want to keep track of specific versions of your project, such as those used in deployments. Use the tagging feature to permanently mark any point in the project's history.

• In your local repository, check out the commit that will be deployed
• Use the Git tag command to create a named reference to the checked-out commit
• Push your tag upstream, where it can be referenced at any point in the future

Tracing Code When collaborating, you need a quick insight into who added or removed code and why. Use the blame feature in forward and reverse order to discover where changes originated from.

• Navigate the repository history to locate a line of code that you need more information about
• Use the Git blame command to see the last person to touch that line of code at that point in history
• If the code has been deleted, use Git blame in the reverse direction to locate the last commit where the line appeared

Where to Go Next? You've acquired substantial knowledge on a powerful versioning tool. Review the lessons learned and get some hands-on experience.

• Review the abstract concepts covered, noting the advantages afforded by distributed version control
• Recall the techniques learned for synchronization and the ways in which choosing different workflows and using distributed control guides our approach to collaboration
• Become well-versed in Git as you contribute to open source projects and create your very own

Learning Git - The Course Overview Get introduced to Git and learn how it can help developers work more efficiently.

• What Git is
• Learn about the different features that Git has to offer

Learning Git - The Course Overview Get introduced to Git and learn how it can help developers work more efficiently.

• What Git is
• Learn about the different features that Git has to offer

Learning Git - The Course Overview Get introduced to Git and learn how it can help developers work more efficiently.

• What Git is
• Learn about the different features that Git has to offer

Learning Git - The Course Overview Get introduced to Git and learn how it can help developers work more efficiently.

• What Git is
• Learn about the different features that Git has to offer

Get introduced to Git and learn how it can help developers work more efficiently.

• What Git is
• Learn about the different features that Git has to offer

Get introduced to Git and learn how it can help developers work more efficiently.

• What Git is
• Learn about the different features that Git has to offer

Git Version Control Version control is very important to track changes when several people are working on a single project.

• What version control is
• How Git approaches version control
• Advantages of distributed version control

Git Version Control Version control is very important to track changes when several people are working on a single project.

• What version control is
• How Git approaches version control
• Advantages of distributed version control

Git Version Control Version control is very important to track changes when several people are working on a single project.

• What version control is
• How Git approaches version control
• Advantages of distributed version control

Git Version Control Version control is very important to track changes when several people are working on a single project.

• What version control is
• How Git approaches version control
• Advantages of distributed version control

Version control is very important to track changes when several people are working on a single project.

• What version control is
• How Git approaches version control
• Advantages of distributed version control

Version control is very important to track changes when several people are working on a single project.

• What version control is
• How Git approaches version control
• Advantages of distributed version control

Choosing a Workflow Different team dynamics requires different collaboration techniques. Choose the workflow that suits your group rong The First Commit After making changes, your project is in a working state, which you need to save before further modifications. Use "git commit" to...