Twitter: https://twitter.com/ben_kadel
Github: https://github.com/kardelio

PART 6 of my Git tutorial series … (More videos coming in the future)

This is the SIXTH video in a series of videos about Git, the fifth video can be found here:
https://youtu.be/y6TDnzqeaqI
And the playlist itself is here:
https://www.youtube.com/watch?v58zsLtwzL60&listPL3Y9MECuxct0RMwdYcqoIjo-7ncRpTNLs

In this particular video (part 6), I explain how every contributor to a codebase SHOULD integrate their new bugfix or feature code into the /"main/" production code (usually the master branch). Users should NEVER push their changes directly to the master branch, and in fact there are usually safeguards in place at the online Git repository providers (such as Github, Bitbucket, and Gitlab) to prevent direct master pushes. Instead, users should work on a separate branch and use a feature called PULL REQUEST to request that their code changes be brought to the master branch (or the specified target branch).

The pull request feature/capability runs on the website of your specified online Git repo provider and is incredibly easy to perform. The code author creates the said pull request with a short message about what their code does and then the pull request can be used by other members of the team or project to /"review" the code before it is merged into the important master/production branch. This review process is called CODE REVIEW.

Code reviews are /"as the name suggests/" another member of your team literally looking at the code you submitted in your pull request and checking it for anything that might prevent it from being successful code or successfully being part of the target branch. Code reviews are made possible by the visually easy to understand CODE DIFFS provided by the online Git repo provider (Github/Bitbucket etc.). These code diffs allow others to quickly and efficiently see all the differences your branch brings. This allows for quick feedback and hopefully approval of the pull request.

Pull requests and code reviews are something that all software development teams (working together on a single code base) do or should do. This way, the code integration process becomes more secure and other developers on the team stay updated on what changes in the code over time. It's an incredibly important process and should never be skipped! Plus, a code review is a really good way to find out where your code could be improved along the way!

There are no new terminal commands in this video. Instead, all the action takes place in the web browser at our chosen online Git repo provider: Github.com.

time stamp

00:00 – Introduction
01:54 – Transfer code to the master
02:28 – Code review
03:05 – Pull request
04:49 – Visual example
05:31 – Importance of code review
05:55 – Pull request demo
09:47 – Code differences
12:28 – Approval of a PR
14:54 – Forking and collaborators
16:29 – Outro
17:00 – Breakdowns

Left

The Git Series repository on Github:
https://github.com/Kardelio/git_series

What is a pull request:
http://oss-watch.ac.uk/resources/pullrequest
https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests
https://www.atlassian.com/git/tutorials/making-a-pull-request

What is a code review:
https://www.atlassian.com/agile/software-development/code-reviews
https://smartbear.com/learn/code-review/what-is-code-review

Best practices for code review:
https://medium.com/palantir/code-review-best-practices-19e02780015f

Link to find and install Git downloads…
https://git-scm.com/downloads

Some more great links to help you on your Git journey…
https://rogerdudler.github.io/git-guide/
https://learngitbranching.js.org/
http://git-school.github.io/visualizing-git/
https://guides.github.com/introduction/git-handbook/

————————————-
Tools:
————————————-
Video editing: https://www.blackmagicdesign.com/products/davinciresolve/
Image editing: https://www.gimp.org/
Camera: Canon M50

————————————-
Credits:
————————————-
Intro map music: https://www.purple-planet.com
Sound effects: http://soundbible.com/
In the video background: Photo by Adrien Olichon from Pexels
Thumbnail background: Pexels.com (no attribution required)

Image: 38

#git #tutorial #terminal

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.