Topic
9 posts tagged “Version Control”.
The Lycoris Team · · 4 min read Git reflog records every place HEAD and branch tips have pointed, letting you recover commits that look lost after a reset, rebase, or deleted branch.
The Lycoris Team · · 5 min read Conventional Commits structures commit messages as type(scope): description so tools can auto-generate changelogs and version bumps from git history.
The Lycoris Team · · 4 min read Git stash saves uncommitted work to a hidden stack so you can switch branches cleanly. How stash, pop, apply, and stash branches actually work.
The Lycoris Team · · 4 min read Git cherry-pick applies one commit's changes onto a different branch without merging the whole branch. How it works, and when to use it instead of merging.
The Lycoris Team · · 4 min read git bisect finds the exact commit that introduced a bug by binary-searching your commit history, cutting the search space in half each step.
The Lycoris Team · · 4 min read A git worktree lets you check out several branches at once in separate folders, sharing one .git history without cloning the repo again.
Takina · · 4 min read Semantic versioning encodes compatibility into a version number's three parts — major, minor, patch — so dependents know what a version bump might break.
The Lycoris Team · · 3 min read Git is a distributed version control system that tracks changes to code and enables collaboration. Learn the core concepts and everyday workflow.
The Lycoris Team · · 5 min read When should you rebase and when should you merge? A clear, example-driven breakdown of the trade-offs, plus a simple workflow you can adopt today.
