Alena  Barton

Alena Barton

1626829320

Branch - Git & Github Tutorial Part 5 | MengSreang Channel

Branch - Git & Github Tutorial Part 5 | MengSreang Channel

👉Download Git Here:
https://www.git-scm.com/download

👉Github Here:
https://github.com

👉Git Document Here:
https://git-scm.com/docs/gittutorial

👉Github Basic Writing and Formatting Syntax Here:
https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax

👉Github Sample README.md Here:
https://gist.github.com/fvcproductions/1bfc2d4aecb01a834b46#repository-title-goes-here
#mengsreang_channel #khmer_git #khmer_github #khmer_web

#git #github

What is GEEK

Buddha Community

Branch - Git & Github Tutorial Part 5 | MengSreang Channel
Alena  Barton

Alena Barton

1626829320

Branch - Git & Github Tutorial Part 5 | MengSreang Channel

Branch - Git & Github Tutorial Part 5 | MengSreang Channel

👉Download Git Here:
https://www.git-scm.com/download

👉Github Here:
https://github.com

👉Git Document Here:
https://git-scm.com/docs/gittutorial

👉Github Basic Writing and Formatting Syntax Here:
https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax

👉Github Sample README.md Here:
https://gist.github.com/fvcproductions/1bfc2d4aecb01a834b46#repository-title-goes-here
#mengsreang_channel #khmer_git #khmer_github #khmer_web

#git #github

Git Rebase Tutorial and Comparison with Git Merge

There are many ways of working with git, if they’re clean, and don’t do damages, probably most of them are good.

But same as space vs. tab, in the IT world is a war between fans of rebase, and fans of git merge.

There are tons of arguments about:

-Which way is better?

-Which one is cleaner?

-Which is more comfortable?

-Which one gives a cleaner git graph?

-Why it’s important, and which one is more dangerous?

#quick help #tutorials #git #git branch #git commit #git interactive rebase

Royce  Reinger

Royce Reinger

1622426929

Git Tutorial: Learn Git Branching in 5 minutes

Git is one of the most widely used version control systems and is an important tool for every developer to know. One of the greatest benefits of Git is its branching capabilities. Git branching is a fundamental aspect of your version control workflow. Today, we’ll discuss how to create, delete, merge, and rebase Git branches. Afterward, we’ll cover the next steps you can take to further your Git knowledge.

We’ll cover:

  • What is branching?
  • Creating branches
  • Deleting branches
  • Merging branches
  • Rebasing branches
  • Git concepts to learn next

What is branching?

Imagine you’re working on a project with your team, and you’re creating a new feature that requires a lot of changes to the codebase. In the process, you discover a bug that needs to be fixed. This bug is related to your new feature, and you don’t want to affect your code. This situation could become complicated. Where will you store the code you’ve been working on?

That’s where Git branches come in. Branching is a core concept of source control that allows you to separate your work into different branches so you can work freely on your source code without affecting anyone else’s work or the actual code in the main branch.

With Git, you begin with a single primary branch called main. Git allows you to create as many branches as you want.

Note: You don’t always have to create branches from the main branch. You can create a new branch from any other branch.

In your separate branches, you’re able to experiment and test without directly affecting your source code. Branching allows you and your team to switch between contexts without worrying about affecting different branches. It’s a great tool for teams because it makes collaboration easier, convenient, and flexible.

Note: Git branches are different from SVN branches. Git branches are useful in your everyday workflow, whereas SVN branches are used in large-scale development efforts.

#computer-science #git #git-branch #github #version-control-system

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 codeSo 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

  1. Are you suppose to check-in all these files?
  2. 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

Madyson  Reilly

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