Lecture

Version Control System: Basics and Workflow

Graph Chat

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.

In course

ENG-270: Computational methods and tools

This course prepares students to use modern computational methods and tools for solving problems in engineering and science. ...

Description

This lecture covers the fundamentals of Version Control Systems (VCS), emphasizing the importance of tracking code changes over time and collaborating effectively. It explains key concepts like repositories, branches, commits, and workflows using Git as an example. The instructor demonstrates common Git operations such as cloning, adding, committing, pulling, and pushing code. Additionally, the lecture delves into branching strategies, including temporary and permanent branches, and best practices for maintaining a stable main branch. Practical examples and step-by-step guides on reverting commits and resolving conflicts are also provided.

Instructor

Satoshi Takahama

Curriculum Vitae (pdf)

Official source

Related concepts (32)

Repository (version control)

In version control systems, a repository is a data structure that stores metadata for a set of files or directory structure. Depending on whether the version control system in use is distributed, like Git or Mercurial, or centralized, like Subversion, CVS, or Perforce, the whole set of information in the repository may be duplicated on every user's system or may be maintained on a single server. Some of the metadata that a repository contains includes, among other things, a historical record of changes in the repository, a set of commit objects, and a set of references to commit objects, called heads.

Comparison of version-control software

In software development, version control is a class of systems responsible for managing changes to computer programs or other collections of information such that revisions have a logical and consistent organization. The following tables include general and technical information on notable version control and software configuration management (SCM) software. For SCM software not suitable for source code, see Comparison of open-source configuration management software.

Atomic commit

In the field of computer science, an atomic commit is an operation that applies a set of distinct changes as a single operation. If the changes are applied, then the atomic commit is said to have succeeded. If there is a failure before the atomic commit can be completed, then all of the changes completed in the atomic commit are reversed. This ensures that the system is always left in a consistent state. The other key property of isolation comes from their nature as atomic operations.

Git

Git (gɪt) is a distributed version control system that tracks changes in any set of s, usually used for coordinating work among programmers who are collaboratively developing source code during software development. Its goals include speed, data integrity, and support for distributed, non-linear workflows (thousands of parallel branches running on different computers). Git was originally authored by Linus Torvalds in 2005 for development of the Linux kernel, with other kernel developers contributing to its initial development.

Distributed version control

In software development, distributed version control (also known as distributed revision control) is a form of version control in which the complete codebase, including its full history, is mirrored on every developer's computer. Compared to centralized version control, this enables automatic management branching and merging, speeds up most operations (except pushing and pulling), improves the ability to work offline, and does not rely on a single location for backups.

Related lectures (48)

Collaborative Data Science: Tools and Techniques

Introduces collaborative data science tools like Git and Docker, emphasizing teamwork and practical exercises for effective learning.

Gitlab Agent for Kubernetes (`agentk`)

Covers the setup of a Gitlab agent for Kubernetes, focusing on installation, version control, and troubleshooting.

Distributed Version Control with Git

Explores Git's distributed version control, covering conflict resolution, collaboration management, and merging in software projects.

Version Control with Git

Introduces version control with Git, focusing on repository setup, committing changes, and collaboration.

Macroeconomic Model Analysis

Explores the impact of productivity shocks and government policies on key economic variables.

Related concepts (32)

Repository (version control)

Comparison of version-control software

Atomic commit

Git

Distributed version control