bluemsi/2nd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: finalized wiki integrity maintenance (v3.0 standard) - pruned 1400+ stubs and fixed 11k+ ghost links

Browse Source
This commit is contained in:
Antigravity Agent
2026-05-02 09:18:34 +09:00
parent c84dcb8371
commit 6445fcc05b
13150 changed files with 55394 additions and 100862 deletions
Download Patch File Download Diff File Expand all files Collapse all files
10_Wiki/Topics_Blog/Git_Workflows.md
+5 -5
View File
@@ -1,13 +1,13 @@
---
id: b2c3d4e5-f6a7-4b8c-9d0e-1f2a3b4c5d6e
category: "[[10_Wiki/Topics/Development]]"
category: "10_Wiki/Topics/Development"
confidence_score: 0.98
tags: [git, workflow, branching, github-flow, git-flow, trunk-based-development, devops]
last_reinforced: 2026-05-01
github_commit: "wikification-git-workflow"
---
# [[Modern Git Workflows & Branching Strategies]]
# Modern Git Workflows & Branching Strategies
## 📌 한 줄 통찰 (The Karpathy Summary)
> 효율적인 Git 워크플로우는 팀의 규모와 릴리즈 주기에 맞춰 선택되어야 하며, Trunk-based Development와 짧은 생명주기의 Feature Branch를 통해 지속적 통합(CI)의 가치를 실현하는 데 목적이 있다.
@@ -33,9 +33,9 @@ github_commit: "wikification-git-workflow"
- **Merge vs Rebase**: Rebase는 깨끗한 히스토리를 제공하지만 강제 푸시(force push) 위험이 있고, Merge는 보수적이지만 히스토리가 복잡해질 수 있다. 팀의 컨벤션 합의가 중요하다.
## 🔗 지식 연결 (Graph)
- **Parent**: [[10_Wiki/Topics/Development]]
- **Related**: [[Engineering Principles (SOLID, DRY, KISS, YAGNI)]], [[CI-CD Pipeline Integration]]
- **Raw Source**: [[00_Raw/Git Flow]], [[00_Raw/Git Workflow]], [[00_Raw/GitHub Flow]], [[00_Raw/Branching Strategies]], [[00_Raw/Trunk-based Development]], [[00_Raw/Atomic Commits]], [[00_Raw/Pull Request (PR)]]
- **Parent**: 10_Wiki/Topics/Development
- **Related**: Engineering Principles (SOLID, DRY, KISS, YAGNI), CI-CD Pipeline Integration
- **Raw Source**: 00_Raw/Git Flow, 00_Raw/Git Workflow, 00_Raw/GitHub Flow, 00_Raw/Branching Strategies, 00_Raw/Trunk-based Development, 00_Raw/Atomic Commits, 00_Raw/Pull Request (PR)
## 💻 GitHub 동기화 자동화 워크플로우
1. Stage: git add .