Experiment: <git init> with examples
The command to create a local repository is git init or git init your-repo
$ git init your-repo # Note: your-repo is the name of your repository
Let us try an example below
Creating a repository without specifying a name, such as “git init“, as a result of this, the present working directory will become a git repository.
Steps to follow:
- Step#1: Create a folder at your desktop
- Step#2: Go to the folder
- Step#3: Right-click in there and open git bash
- Step#4: Execute the command “git init”
Gitbash command line output will look like this,
$ git init Initialized empty Git repository in C:/Users/admin/Desktop/New folder/.git/
Reviewing the status of your newly created git repository
[email protected] MINGW64 ~/Desktop/New folder (master) $ git status On branch master No commits yet nothing to commit (create/copy files and use "git add" to track) [email protected] MINGW64 ~/Desktop/New folder (master) $
How to get quick git bash command-line help using git help?
$ git help usage: git [--version] [--help] [-C <path>] [-c <name>=<value>] [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path] [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare] [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>] <command> [<args>] These are common Git commands used in various situations: start a working area (see also: git help tutorial) clone Clone a repository into a new directory init Create an empty Git repository or reinitialize an existing one work on the current change (see also: git help everyday) add Add file contents to the index mv Move or rename a file, a directory, or a symlink reset Reset current HEAD to the specified state rm Remove files from the working tree and from the index examine the history and state (see also: git help revisions) bisect Use binary search to find the commit that introduced a bug grep Print lines matching a pattern log Show commit logs show Show various types of objects status Show the working tree status grow, mark and tweak your common history branch List, create, or delete branches checkout Switch branches or restore working tree files commit Record changes to the repository diff Show changes between commits, commit and working tree, etc merge Join two or more development histories together rebase Reapply commits on top of another base tip tag Create, list, delete or verify a tag object signed with GPG collaborate (see also: git help workflows) fetch Download objects and refs from another repository pull Fetch from and integrate with another repository or a local branch push Update remote refs along with associated objects 'git help -a' and 'git help -g' list available subcommands and some concept guides. See 'git help <command>' or 'git help <concept>' to read about a specific subcommand or concept.