https://dailypypy.org/tags/commit-graph/ Recent content in Commit-Graph on 每日拍拍 Hugo -- gohugo.io zh-tw © 2026 每日拍拍 Sat, 10 Oct 2026 10:49:00 +0800 155076163427069952 154825760438254592 https://dailypypy.org/learn/git-maintenance-commit-graph/ Sat, 10 Oct 2026 10:49:00 +0800 https://dailypypy.org/learn/git-maintenance-commit-graph/ <!--- 1440x768 prompt: masterpiece, best quality, highres, clean anime illustration, japanese anime style, soft shading, flat color design, 1girl, black hair, green eyes, white off-shoulder shirt, black short skirt, eye-level medium full shot, side profile, looking over shoulder, holding one translucent stack of blank cards close to her chest, calm capable smile, looking at viewer, pastel sage green and warm cream background, subtle floating connected nodes and layered archive shapes without symbols, logos, markings, numbers, letters, or text, neat composition, detailed eyes, cute and smart vibe, minimal background, polished illustration, no text negative prompt: worst quality, bad eye, bad hand, extra limbs, manga, multiple views, monochrome, text, signature dedup note: Planned 2026-10-10 topic `git-maintenance-commit-graph` passed a strict 186-post inventory and current-source scan. ../git-sparse-checkout/ reduces a monorepo working tree, while ../git-rerere/ stores reusable conflict resolutions and only briefly discusses its own cache cleanup. No existing post covers git maintenance, commit-graph, multi-pack-index, scheduled repository upkeep, or before/after performance measurement. This focused follow-up stays on object-database maintenance, safe scheduling, verification, and rollback-friendly cleanup. source check: Reviewed against the current official Git maintenance, commit-graph, multi-pack-index, count-objects, gc, and Trace2 documentation on 2026-10-10. Commands were checked with Apple Git 2.50.1; examples favor `git maintenance` tasks and explicitly avoid unsafe concurrent pruning. ---> <p>大型 Repository 用久了，常會出現一些很難描述的「鈍」：</p>