Skip to main content

🔧 Introduction to Git

What is Git?​

Git is a distributed version control system that allows you to record and manage changes made to files over time.
It was created by Linus Torvalds in 2005 with the goal of helping developers collaborate on projects without losing the history of modifications.

Git not only tracks versions, but also allows you to experiment risk-free, work in a team, and maintain full control over a project.

What is Git used for?​

  • Keep a detailed history of changes in a project
  • Facilitate collaboration among multiple people
  • Test new ideas without affecting the stable code version
  • Integrate continuous deployment and automation tools (CI/CD)
  • Restore previous project versions in case of errors

Importance of Git for teams and companies​

Git is an essential tool for development teams and modern companies:

  • Efficient collaboration: multiple developers can work in parallel without conflicts.
  • Transparency and traceability: each change is recorded with author, date, and purpose.
  • Code review: allows evaluating and approving changes before integrating them into the project.
  • Integration with platforms like GitHub, GitLab or Bitbucket to manage tasks, issues, and deployments.
  • Improves software quality through workflows like Pull Requests, testing branches, etc.

Companies that adopt Git optimize their development processes, improve communication between teams, and reduce errors in production.

Git Standardization​

Standardization in Git refers to establishing clear and consistent conventions for using Git within a team or project. This improves organization and avoids common problems.

Common best practices​

  • Clear commit messages:
    feat: add registration form
    fix: correct email validation error

  • Branches by purpose:

    • main: stable version
    • develop: integration of new features
    • feature/*: new features
    • bugfix/*: corrections
    • hotfix/*: urgent fixes

  • Descriptive branch names:
    feature/login, bugfix/404-error, hotfix/token-expired

  • Use of .gitignore to exclude unnecessary or sensitive files (like node_modules/, .env, etc.)

  • Pull Requests for review and quality control

Standardization facilitates collaborative work and ensures that everyone follows the same technical language within the project.

Commit conventions​

info

Navigate to the following link to go to the page that explains best practices and standardizations for using git.

Conventional Commits URL