Repository Management

• git init → Initialize a new Git repository
• git clone <repo-url> → Clone an existing repository
• git remote add origin <url> → Add a remote repository
• git remote -v → List remote repositories
• git remote remove <name> → Remove a remote

git init

Syntax : git init [options] [<directory>]

# Initialize in current directory:
git init

# Initialize in a new directory:
git init my-project

# Set initial branch name explicitly:
git init -b main

# Create a bare repository:
git init --bare /srv/git/my-project.git

• Description: The git init command is the foundation of Git usage. Whether you’re starting a new project, reinitializing an existing one, or setting up the bare repo for collaboration, git init is the first step in managing code with Git.
• Usage: It creates the repository structure with .git, sets up the initial branch (default is main in modern Git), and prepares the repository to start tracking files and commits.
• Think Tank: Git repositories can be initialized in different contexts:

• Best Practices:
  • Always set the initial branch name (-b main) for consistency
  • Use --bare only for server-side repositories
  • Initialize repos inside project directories, not system folders
  • Add a .gitignore immediately to avoid tracking unwanted files
  • Commit an initial README or setup file after initialization

Git - git-init Documentation

git-init Documentation

git clone

Syntax : git clone <repo-url> [directory]

# Clone a remote repository:
git clone https://github.com/user/project.git

# Clone into a specific directory:
git clone https://github.com/user/project.git my-project

# Clone with SSH:
git clone git@github.com:user/project.git

# Shallow clone (last 1 commit):
git clone --depth 1 https://github.com/user/project.git

# Bare clone:
git clone --bare https://github.com/user/project.git

# Mirror clone:
git clone --mirror https://github.com/user/project.git

• Description: The git clone command creates a copy of an existing Git repository into a new directory.
• Usage: It downloads the full history, sets up remotes (Default is origin), and prepares a working directory.
• Think Tank: Whether you’re cloning for development, backup, or CI/CD, understanding shallow, bare, and mirror options ensures you use the right strategy for your workflow. Git supports different cloning modes:

• Best Practices:
  • Use shallow clones for CI/CD pipelines to save time and bandwidth
  • Always verify remote URLs before cloning (especially with SSH)
  • Use --recurse-submodules if the project depends on submodules
  • Prefer mirror clones for backups, not for everyday development
  • Keep cloned repos updated with git fetch or git pull

Git - git-clone Documentation

git-clone Documentation

git remote basics

• Remote repository: A version of your project hosted elsewhere (server, cloud, another machine).

git remote add origin https://github.com/user/project.git

Here, origin is the alias for the GitHub repo URL.

• Remote name: A short alias for the repository URL (commonly origin).
• Remote URL: The actual location (HTTPS, SSH, or local path).

git remote

Syntax : git remote [options] [subcommand] [name] [url]

# List remotes: → Shows remote names and URLs.
git remote
git remote -v

# Add a remote:
git remote add origin https://github.com/user/project.git

# Remove a remote:
git remote remove origin

# Rename a remote:
git remote rename origin upstream

# Change remote URL:
git remote set-url origin git@github.com:user/project.git

# Show remote details:
git remote show origin

• Description: The git remote command manages the list of remote repositories that your local Git repository can interact with.
• Usage: It lets you add, remove, rename, and inspect remote connections, defines shortcuts (like origin) for repository URLs, enables collaboration by linking your local repo to shared repos (e.g., GitHub, GitLab, Bitbucket).
• Think Tank: Remote options to work with:

• Best Practices:
  • Always check remotes with git remote -v before pushing
  • Use clear names (origin for your fork, upstream for the main repo)
  • Prefer SSH URLs for secure authentication
  • Regularly prune remotes to avoid clutter
  • Document remote setup in project onboarding guides

Git - git-remote Documentation

git-remote Documentation