Git Tutorial for Beginners - Git & GitHub Fundamentals In Depth

This Git tutorial for beginners is designed to teach you the Git command line tool and how it works with Github. This beginner Git tutorial teaches Github fundamentals and explains concepts like branches, pushing, merge conflicts and many other useful Git commands. It goes through the Git workflow and illustrates how Git and Github work on a lower level.

💻 Git Download: https://git-scm.com/
🖱 GitHub Website: https://github.com/

⌨ Common GitHub Commands ⌨

To create a new repository locally: git init
To add files to staging area: git add . OR git add ~filename~
To check status of staging area: git status
To commit new changes: git commit -m “commit message”
To create a new branch: git checkout -b ~branch name~
To switch between branches: git checkout ~branch name~
To merge branches together: git merge ~branch name~
To add a remote repository: git remote add ~remote name~ ~https://yourremoteurl~
To pull changes from a remote repository: git pull ~remote name~ ~branch name~
To push changes to a remote repository: git push ~remote name~ ~branch name~

⭐️ Timestamps ⭐️

00:00 - Introduction
01:22 - Git vs GitHub
03:00 - GitHub Workflow
07:09 - Git History and Branches
15:15 - GitHub UI Example
16:51 - Git Setup
18:53 - Basic Git Commands
24:24 - Branches
28:43 - Remote Repositories
33:08 - Global Config
35:09 - More Examples

#git #github #developer

What is GEEK

Buddha Community

Git Tutorial for Beginners - Git & GitHub Fundamentals In Depth

Andreanne Kassulke

1597916460

7 Best Practices in GIT for Your Code Quality

There is no doubt that Git plays a significant role in software development. It allows developers to work on the same code base at the same time. Still, developers struggle for code quality. Why? They fail to follow git best practices. In this post, I will explain seven core best practices of Git and a Bonus Section.

1. Atomic Commit

Committing something to Git means that you have changed your code and want to save these changes as a new trusted version.

Version control systems will not limit you in how you commit your code.

You can commit 1000 changes in one single commit.
Commit all the dll and other dependencies
Or you can check in broken code to your repository.

But is it good? Not quite.

Because you are compromising code quality, and it will take more time to review code. So overall, team productivity will be reduced. The best practice is to make an atomic commit.

When you do an atomic commit, you’re committing only one change. It might be across multiple files, but it’s one single change.

2. Clarity About What You Can (& Can’t) Commit

Many developers make some changes, then commit, then push. And I have seen many repositories with unwanted files like dll, pdf, etc.

You can ask two questions to yourself, before check-in your code into the repository

Are you suppose to check-in all these files?
Are they part of your source code?

You can simply use the .gitignore file to avoid unwanted files in the repository. If you are working on more then one repo, it’s easy to use a global .gitignore file (without adding or pushing). And .gitignore file adds clarity and helps you to keep your code clean. What you can commit, and it will automatically ignore the unwanted files like autogenerated files like .dll and .class, etc.

#git basics #git command #git ignore #git best practices #git tutorial for beginners #git tutorials

Jeromy Lowe

1599097440

Data Visualization in R with ggplot2: A Beginner Tutorial

A famous general is thought to have said, “A good sketch is better than a long speech.” That advice may have come from the battlefield, but it’s applicable in lots of other areas — including data science. “Sketching” out our data by visualizing it using ggplot2 in R is more impactful than simply describing the trends we find.

This is why we visualize data. We visualize data because it’s easier to learn from something that we can see rather than read. And thankfully for data analysts and data scientists who use R, there’s a tidyverse package called ggplot2 that makes data visualization a snap!

In this blog post, we’ll learn how to take some data and produce a visualization using R. To work through it, it’s best if you already have an understanding of R programming syntax, but you don’t need to be an expert or have any prior experience working with ggplot2

#data science tutorials #beginner #ggplot2 #r #r tutorial #r tutorials #rstats #tutorial #tutorials

Madyson Reilly

1604109000

Best Practices for Using Git

Git has become ubiquitous as the preferred version control system (VCS) used by developers. Using Git adds immense value especially for engineering teams where several developers work together since it becomes critical to have a system of integrating everyone’s code reliably.

But with every powerful tool, especially one that involves collaboration with others, it is better to establish conventions to follow lest we shoot ourselves in the foot.

At DeepSource, we’ve put together some guiding principles for our own team that make working with a VCS like Git easier. Here are 5 simple rules you can follow:

1. Make Clean, Single-Purpose Commits

Oftentimes programmers working on something get sidetracked into doing too many things when working on one particular thing — like when you are trying to fix one particular bug and you spot another one, and you can’t resist the urge to fix that as well. And another one. Soon, it snowballs and you end up with so many changes all going together in one commit.

This is problematic, and it is better to keep commits as small and focused as possible for many reasons, including:

It makes it easier for other people in the team to look at your change, making code reviews more efficient.
If the commit has to be rolled back completely, it’s far easier to do so.
It’s straightforward to track these changes with your ticketing system.

Additionally, it helps you mentally parse changes you’ve made using git log.

#open source #git #git basics #git tools #git best practices #git tutorials #git commit

Joseph Norton

1592616120