Git on Jeanphilo Blog

Write Clear Issues with Templates: From Zero to GitHub Issue Forms

Tue, 11 Nov 2025 00:00:00 +0000

Title (accurate and keyword-rich)

Write Clear Requirements with Issue Templates: A Complete Guide to GitHub Issue Forms

Subtitle / Abstract

This post teaches you how to configure GitHub Issue templates for feature requests and bug reports, including folder structure, YAML forms, Markdown templates, and common pitfalls. It is ideal for teams that want clearer requirements and less back-and-forth.

Target readers

This article is for:

Backend/frontend/full-stack engineers who create Issues regularly
Leads/TLs/architects who want standardized requirement intake
Mid-level developers familiar with GitHub but new to Issue templates

Beginners can follow, but basic GitHub knowledge is assumed.

How to Set Up Gitea

Tue, 28 Oct 2025 00:00:00 +0000

Run Gitea Locally: Your Private GitHub (with Existing Repo Import)

Subtitle / Abstract: This guide walks you through installing the lightweight Git server Gitea on your local machine. No root required, no system pollution. Manage, browse, and push projects like GitHub, and import existing repos.

Target readers: Personal developers, indie engineers, and small team leads with basic Git knowledge.

Background / Motivation

Many developers want:

to host code inside a company or LAN
to avoid cloud platforms (GitHub/Gitee)
to have a web UI, pull requests, and code browsing

GitLab is heavy (often multiple GB of RAM). Gitea is:

Conventional Commits: Make Team Collaboration and Automation Efficient

Sat, 25 Oct 2025 00:00:00 +0000

Title

From feat to fix: master Git commit conventions for collaboration and automation

Subtitle / Abstract

A practical guide to Conventional Commits. Learn commit types (feat:, fix:), write clean messages, and enable automatic changelogs and releases.

Target readers

Beginners: new to Git, want better commit habits.
Mid-level devs: want commits friendly to team and CI.
Leads/architects: want a consistent team standard.

Background / Motivation

Most commit messages look like:

“update code” “fix bug” “some changes”

LAN Git Bare on WSL2

Wed, 22 Oct 2025 00:00:00 +0000

Access a Git Bare Repo on Windows WSL2 from the LAN

In development, you often need to share Git repositories across multiple machines. If you use WSL2 on Windows and want other LAN machines to access a Git bare repo inside WSL2, this guide walks you through the setup.

1. Create a Git bare repo in WSL2

In WSL2, go to the target directory:

git init --bare my_project.git

my_project.git is a bare repo with no working tree, only Git data.
A bare repo behaves like a remote and can be cloned and pushed.

2. Enable SSH in WSL2

Other machines will access via SSH.

Git Branch Workflow for Small Teams

Mon, 20 Oct 2025 00:00:00 +0000

Simplified Git Branch Workflow (Solo / Small Team)

This workflow is a simplified version of Git Flow. It is suitable for personal projects or small teams: structured but not heavy.

1. Main branch (long-lived)

main
- Always stable and release-ready
- Production deployments come from here

For small teams, main is usually enough; no need for develop.

2. Feature development (feature branch)

Naming: feature/<feature-name>
Purpose: build new features, then merge back to main

Examples:

Use a Local Git Bare Repo to Separate Dev and Test Environments

Mon, 20 Oct 2025 00:00:00 +0000

Use a Local Git Bare Repo to Separate Dev and Test Environments

In full-stack work, a common problem is how to isolate dev and test environments. Many people host on GitHub or GitLab, but private projects may not be suitable for public hosting.

Git is distributed. You can set up a local bare repo as a remote to move code from dev -> test in one machine.

What is a bare repository?

A normal repo (git init) has a working tree + .git metadata and can be edited directly.
A bare repo (git init --bare) has only Git data, no working tree. It is usually used as a remote.

In short: