Fundamentos de Git desde la línea de comandos

Welcome to Git basics! Git is a powerful Version Control System (VCS). Think of it as a super-smart history book for your code.

It tracks every change you make, letting you revert to older versions, collaborate with others, and manage different features without stepping on toes. It's essential for modern software development!

To begin tracking a project with Git, you first need to initialize a repository. This creates a special .git folder in your project, where Git stores all its tracking information.

Use the git init command in your project's root directory.

Before saving your work, Git uses a 'staging area'. This is like a rough draft space where you select which changes you want to include in your next save.

The git add command is used to add files or changes to this staging area.

Once changes are staged, you 'commit' them. A commit is a snapshot of your project at a specific point in time, with a descriptive message.

Use git commit -m "Your message" to save staged changes to your repository's history.

Git keeps a detailed log of all your commits. You can review this history to see who made what changes and when.

The git log command displays your repository's commit history. The --oneline option provides a concise view.

Branches are a core concept in Git. They allow you to diverge from the main line of development and continue working without affecting the main project.

• Work on new features.
• Fix bugs without breaking stable code.
• Experiment with new ideas.

The main (or master) branch is typically the stable version.

To start a new line of development, you create a new branch. This doesn't move you to the new branch yet; it just creates it.

The git branch <branch-name> command creates a new branch. You can list all branches with just git branch.

After creating a branch, you need to switch to it to start working on that specific line of development. Your files will reflect the state of that branch.

Use git switch <branch-name> to move to an existing branch. It's the modern way to navigate branches.

Once you've finished work on a feature branch, you'll want to integrate those changes back into your main development line, usually the main branch.

First, switch to the target branch (e.g., main), then use git merge <source-branch> to bring in the changes.

You've learned the core steps for managing changes with Git. Let's test your understanding of how to save your work.

Great job! You've learned the fundamental Git commands:

• git init: To start a new repository.
• git add: To stage changes for a commit.
• git commit: To save staged changes to history.
• git log: To view your project's commit history.
• git branch: To create and list branches.
• git switch: To move between branches.
• git merge: To combine changes from different branches.

These commands form the backbone of managing your code with Git!