How to use Git and Git Bash in the area: The perfect guide

Introduction

GIT Distributed Type Type version that helps track changes in your code, share with others, and save the history of your project. Git Bash is the Terminal Windows app that provides unix-like experience of Git.

This guide will travel by Setup GIT, using Git Bash, and read the key to local advancement git advancement.

Installation

Windows

1. Download Windows Git from Git-Scm.com
2. Run the installer with default options (or customize as required)
3. Git bag will be automatically installed as part of the package

Macos

1. Add GIT using HomeBrew: Brew to install git
2. Otherwise, Download from git-scm.com

The Glass

• On Debian / Ubuntu: sudo apt-get inserting git
• For Fedora: sudo DNF to insert git
• For others is delivered, use the correct package manager

Inserting the installation

Open Git Bash (Windows) or Terminal (Macos / Linux) and type:

This should indicate the type of git installed.

Git bag bases

Git bag provides shell-like shell experience. Here are some important instructions:

Instructions for wandering

• PWD – Active Printing of Directory
• LS files – List files and brochures
• ch [directory] – change directory
• MKDIR [directory] – Create a new directory
• captain [file] – Remove File
• rm -r -r [directory] – Delete directory and contents

File performance

• contact [filename] – Create an empty file
• cat [filename] – Display file content
• spy [filename] or vim [filename] – Edit files in the Forum

Keyboard shortcuts

• CTRL + C – Complete current command
• CTRL + L – Wipe Screen
• Tab – complete auto orders or file names
• Top arrows / down – Navigate to the command history

The configuration of git

Before using git, prepare your ownership:

Further configuration

Set your default editor:

Enable colorful exit:

View all Configuration:

The Basic Works of Git

It starts the warehouse

Navigate to your project folder and start the storage area:

Check-up condition

See which files are followed, converted, or edited:

Files that use style

Enter files in a catch place:

To make changes

Save the slapped changes in the last place:

Or open the editor to write a multiple detail message:

Viewing History

Marriage and Collect

Working with Branches

Create a new branch:

Switch to the branch:

Create and switch to a new branch in one command:

Write all branches:

Integrating the branches

Mix changes from one branch in your current branch:

Management Join Conflicts

When git can automatically link changes, you will need to resolve conflicts:

1. Git will notice opposing files
2. Open files and look at conflict marks (<<======, >>>>>>>>>>
3. Edit files to resolve conflicts
4. Enter resolved files: git enter
5. Complete the Test: Git Commitment

Deleting Branches

Remove the branch after combining:

Remote remofistories

Adding the final place away

To view remote remospores

Pressure in Remotionery Remote

Pulling from a desert place

To compile the warehouse

Advanced GIT commands

Change of Reformation

Save temporarily modified files to apply to something:

Return to Reform

Undo to do:

Reset in the past (use with caution):

Viewing and comparing changes

Active Revenge

Rewrite, Squash, or re-arranged,

Troubleshooting

Normal issues and solutions

Problem: “Fatal: Not a Destruction”

• Solution: Make sure you are in the right identification or launch the last git Init

Problem: Can't push in the final place away

• Solution:
  • Check if you have the right permit
  • Pull the latest changes first: git garden
  • Check that Remote URL is OK: GIT Remote -V

Problem: Mix the conflicts

• Solution: Solve conflicts manually, and git add resolved files and offer yourself

Problem: Accidental commitment

• Solution: Use the Git Reset of the Back ~ 1 to fix the last commitment while keeping changes

The best habits

1. Are always willing with clear, descriptive messages
2. Create branches With new features or adjustments
3. Pull before pressing To minimize conflicts
4. Write messages with purpose explaining why changes
5. Use .gitignore To remove unnecessary files (creativity, leaning, etc.)
6. Review the change Before the Git Diff and Git Meaning
7. Save You Keep Fine On one reasonable change
8. Use tags Marketing or Important Releases
9. Back up your repositories regularly
10. Write your git function of your git Group cooperation

.Gitignere for an instance

Create a .gitignine file in your database:

Customize this file according to certain requirements for your project.

Store

GIT and GIT Bash provide powerful translation tools and cooperation. In this guide, we cover the installation of all platforms, key principles of the basic performance, temperature strategies, remote storage strategies, and developed activities such as restrictive and recovery activities. We also viewed regular problems for resolving problems and practices that keep the pure work movement. Through these basic bases, you are now equipped to track changes, work effectively, and save the organized history of your projects.