Effective Commit Message Writing Guidelines

In software development, version control is an essential aspect. Among its various components, commit messages play a pivotal role in maintaining project history and facilitating seamless team collaboration. Well-written commit messages not only ease code reviews but also simplify bug tracking and enhance the overall quality of a project. In this article, we will delve into the guidelines for writing effective commit messages and explore their significance. 1. Separate Subject from Body: Convey Crisp Information A commit message should be structured with a subject and a body. This enables a quick grasp of the gist and allows for detailed inspection when necessary. ...

July 12, 2024 · 4 min · 686 words · In-Jun Hwang

Deleting Branches After Merge: Why and How

Step-by-step Breakdown of Merging Create a new branch: Create a new branch from the main branch using git checkout -b <new-branch-name>. Add commits to the branch: Make code changes in the new branch and commit them in meaningful units. Push to remote repository: Upload your working branch to the remote using git push origin <branch-name>. Create a pull request: Create a pull request on platforms like GitHub to request merging of your changes. ...

July 11, 2024 · 2 min · 338 words · In-Jun Hwang

Git Branching Strategies: Comparing Git Flow and GitHub Flow

Version control is a crucial aspect of modern software development. Git, a distributed version control system, empowers multiple developers to work concurrently. To leverage Git’s benefits, a structured branching strategy is essential. This article provides an in-depth analysis and comparison of Git Flow and GitHub Flow, two of the most widely adopted Git branching strategies. Git Flow: The Standard for Structured and Rigorous Versioning Git Flow is a branching strategy proposed by Vincent Driessen in 2010, designed to provide a systematic approach to managing a software development lifecycle. The model employs five core branches: ...

July 10, 2024 · 4 min · 703 words · In-Jun Hwang

How to Use Git: From Basic to Advanced

About: Git is a must-have distributed version control system for developers. It tracks changes to source code over time and helps multiple developers collaborate more efficiently. In this post, we’ll take an in-depth look at the core concepts of Git, cover essential commands in detail, along with real-world use cases and useful options of each command. Understanding the Basic Structure of Git Git consists of four major areas: Working Directory: The place where the actual files reside. This is where you write and modify your code. Staging Area: A place to temporarily hold changes that are ready to be committed. Local Repository: Where your committed versions are stored. Remote Repository: A repository on a server that is shared with your team. Understanding this structure will help you grasp the behavior of Git commands more easily. ...

July 8, 2024 · 6 min · 1096 words · In-Jun Hwang

Vim Usage Guide

Vim is an advanced version of the Vi editor that provides more features while including the features of Vi. Vim can be operated with just the keyboard, enabling users to edit text rapidly without using a mouse. This post will summarize the basic usage and commands of Vim. Vim Modes Vim is divided into three main modes. Normal mode: This is the basic mode in which you can edit text or enter commands. Insert mode: This mode allows you to enter text, and you can add or modify text. Visual mode: This mode enables you to select text, and you can copy or delete the selected text. Normal Mode When you launch Vim, it starts in Normal mode by default. You can use the following commands in Normal mode. ...

July 6, 2024 · 3 min · 431 words · In-Jun Hwang