
Learn how version control uses git and GitHub to manage change history across a distributed version control system with local and remote repositories, prevent conflicts, and recover versions.
Learn to set up Git and GitHub, install Git and Visual Studio Code, and use the Git Graph extension to visualize Git history across macOS and Windows.
Learn to access GitHub, sign up and create an account, then navigate your profile, repositories, and project boards to manage remote repositories and collaborators.
Understand the basic flow of source management in git and GitHub, including local and remote repositories, working tree, staging area, and commits with git add, commit, push, pull, clone.
Learn to create a Git local repository, configure users, ignore untracked files, and manage changes with git add, commit, and log using VSCode terminal.
Access GitHub in a browser to create a public remote repository, copy its URL, add it to your local repo, and push commits while resolving authentication prompts.
Learn to clone a remote repository to a local Git repository using VSCode and GitHub, set up user credentials with git config, and fetch updates with git pull.
learn how to push after commit by following the flow from remote to local to remote repositories, including git pull, git add, git commit, and git push.
Learn how Git stores changes as snapshots and uses commit history, and manage branches with checkout, log, and merge on the main branch.
Act as the team leader and admin to create a private remote repository, initialize a local git repo, set up the project environment, and add collaborators for git-flow.
Learn to prepare collaboration with team members by setting up a local Git repository, cloning from a remote repository, configuring user identities, and initializing Git flow in VSCode.
Master the feature branch strategy in git flow for team collaboration. Learn starting, publishing to origin, tracking, reviewing via pull requests, and finishing by merging into the develop branch.
As a team leader, manage a GitHub project by creating a public project board, adding feature labels, publishing issues, assigning teammates, and tracking contributions.
Master git-flow by practicing feature branches, resolving three issues, and creating and approving pull requests. Learn fast-forward and auto-merge strategies when merging into develop.
Learn feature branch tracking with git-flow: start, track, and finish a feature branch from develop, publish via pull requests, and synchronize local and remote repositories.
Master the release branch strategy in git flow for team projects. Create release branches from develop, test, merge into main and develop, tag versions, and finish with git flow commands.
Learn to manage releases with git-flow by creating and publishing a release branch, tracking QA tasks, handling pull requests, merging, and finishing the release.
Jump into the hotfix branch in git flow to urgently fix production issues, branching from main, merging into develop and main, and tagging the release.
Learn to execute a hotfix with git-flow, create and close hotfix branches, publish a pull request for review, merge into main and develop, and push tags reflecting urgent bug fixes.
Not sure how Git and GitHub are being used at work?
Using Git at work means that you are proficient in using it as a tool for collaboration in software development. However, it is not enough to simply know the features or commands of Git and GitHub. You need to be able to set up standard Git Flow policies for collaboration at work, and you need to be able to work seamlessly with your coworkers based on those policies.
By the end of this course, you will be able to set up and use Git Flow policies from scratch, even if you know nothing about Git and version control, and you will have the skills to follow your team's Git Flow policies and apply them to your work.
Experience how professional developers actually use Git and GitHub through a variety of scenarios and role-play the roles and situations you might encounter in the workplace. It's time for you to master Git and GitHub.
(POINT 1) You will be able to use Git and GitHub in the workplace, even if you don't know anything about Git or version control.
(POINT 2) You will be able to set up a standard Git Flow policy for collaboration at work and follow that policy to collaborate effectively with coworkers.
(POINT 3) You will learn the basics of Git and GitHub, from basic features to collaboration, through practical examples in role-specific scenarios.
(POINT 4) You will learn Git and GitHub in a variety of operating system environments, including Windows, macOS, and Linux.
(POINT 5) You will learn in-depth knowledge of Git and GitHub required in the workplace as senior developers are dedicated to answering Q&As on the course.
Section 1: Git & GitHub for Team Projects
Understand the need for versions and version control systems, and prepare your environment for the practice ahead.
Section 2: Learn Basic Git Commands
Learn the basic flow of source management in Git and GitHub, and explore Git's key commands for project management. You set up your project as a Git repository with practice managing a personal project with Git. You walk through the process of creating a commit of a file to version control and then pushing it to a remote repository on GitHub.
Section 3: Git Flow
Learn the concept of a branch in Git and Git Flow. You build an environment for Git Flow and prepare for a team project practice. In this practice, there will be two roles: team leader and team member, and you do practice specific to each role.
Section 4: Scenario 1 - Feature Development
In the first Git Flow scenario, you create a feature branch for feature development. At a workplace, there are many requirements coming in from different teams. To effectively manage these requirements, you learn about GitHub's features, how to create and manage issues, and how to use projects boards.
Section 5: Scenario 2 - Launch
In the second Git Flow scenario, you create a release branch for a release. When releasing a developed code version of a team's project at the workplace, you create a release branch, have it tested by the Quality Assurance (QA) team, address identified issues, and proceed with release-focused tasks. Let's try this release-focused practice.
Section 6: Scenario 3 - Hotfix
In the third Git Flow scenario, you create a hotfix branch to urgently fix a bug in a released version. The hotfix branch is a branch used for unplanned deployments, and it is created in response to an immediate issue with the stability of the deployed code. In this scenario, you practice closing a branch after resolving a critical bug in operation with a hotfix branch.