Refresher on GitHub Concepts

1. Refresher on GitHub Concepts

Welcome to Intermediate GitHub Concepts!

2. Your instructors

My name is Arne. With a PhD in Economics and Statistics and over a decade of experience in data science, I bring my expertise to this course which was co-created by Stan Konkin from DataCamp.

3. Course overview

In this course, we’ll cover: Setting up, automating, and gaining insights with GitHub Projects; Best practices for GitHub administration and authentication; Managing an InnerSource program and ensuring secure development. We'll teach these concepts using examples from the daily routines of a data team in an e-commerce company. But first, let's recap GitHub basics: repositories, branches, pull requests, issues, reviews, and merges.

4. Repositories

Repositories, or repos, are like digital folders that store a team’s files, history, and joint efforts all in one place. They can be private or public, making it easy to manage and share the team's work. For this course, we created the ecommerce-data-hub repository, which includes several folders like scripts and pipelines, along with a README.md file that provides a description of the repo.

5. Branches

Branches are like different versions of files in a repository, allowing team members to work on tasks without affecting the main code. The main branch, called master, holds the live version of the project. Other branches are for bug fixes and extensions.

6. Issues

GitHub issues are used to track problems, plan tasks, and communicate important updates, helping team members manage and discuss project details efficiently. In our repo, we have two issues: updating the pipeline and reviewing campaign results. Remember, you can assign these tasks to your colleagues.

7. Pull requests and reviews

A pull request on GitHub is a way to propose changes to a repository. It lets team members review and discuss the changes before they are added to the main codebase. Reviews on GitHub ensure code quality. When a pull request is made, team members can review the changes, add comments, and propose improvements. Reviewers can approve the changes or request modifications, ensuring only reviewed code gets merged into the main branch.

8. Merges

Merging a pull request integrates the proposed changes into the main branch. This step finalizes the review process, combining the new code with the existing project.

9. Let's practice!

Now that we've recalled the basics, it's time for practice!

Create Your Free Account

By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.