sinpro.dev
Docs
Dev Environment
VSCode Workspace Extensions
  • Company Information
    • Portfolio
    • About
    • Services
    • Events
  • Dev Environment
    • macOS Settings
    • Chrome Extensions
    • VSCode Workspace Settings
    • VSCode Workspace Extensions
    • Global NPM Packages
    • npm-check-updates
    • SvelteKit
    • Customize Zsh
    • ChatGPT Prompts
    • Tailwind CSS
    • Warp
    • Keyboard Shortcuts
  • Assets
    • Assets
    • JPG/PNG to AVIF
    • TTF to WOFF2
  • Clean Code
    • Clean Code
    • Format
    • Quality
    • Variables
    • Functions
    • Objects and Data Structures
    • Classes
    • Concurrency
    • Error handling
    • Comments
  • Code Style
    • TypeScript Config
    • Prettier
    • ESLint
    • Stylelint
  • Testing
    • Vitest
    • Playwright
  • Git
    • Git Branches and Commits
    • Git Hooks
    • Git User Profiles
    • Git for Windows
  • GitHub
    • GitHub Issues
    • GitHub Pull Requests
    • GitHub Repository Settings
    • GitHub Branch Protection
    • GitHub Actions
  • Code Quality
    • SonarCloud Coverage
  • Server
    • SSH
    • PM2
    • Caddy
    • Updating the server
    • ngrok
  • Team sinProject
    • Our Team Policy
    • Equipment and Supplies
    • Books
    • Slack
    • Locales
    • Funny Apps
    • Docs History
  • Talk
    • Talk
    • Creating a Project
    • App Structure

Git

Git Branches and Commits

Edit this page

Branching Strategy

At first, we employed git-flow and managed multiple branches such as develop, feature, release, hotfix, and master. However, after years of operation and trial and error, we now simply use only the main branch as the integration branch and topic branches.

Git branch naming conventions

Write the issue number and issue title in kebab-case, connected with a hyphen.

Markdown
743-git-branches-and-commits

Script

We have prepared a script to create branches issue names.

Bash
npm run branch "<branch-name> #<branch-number>"

example:

Bash
npm run branch "Correct English #990"

Commit message conventions

Include the issue title and issue number.

Markdown
Git Branches and Commits #743

If there are multiple commits in the same branch, provide additional details.

Markdown
Git Branches and Commits #743 Update docs
Playwright Git Hooks
© sinProject. v0.73.0
On this page
  • Git Branches and Commits
  • Branching Strategy
  • Git branch naming conventions
  • Script
  • Commit message conventions