#Version-Control
16 notas · última:
Understanding Git Submodules: A Comprehensive Guide
The page explains what Git submodules are, why to use them, and how to add, clone, update, remove them on Windows, and keep them under control in projects.
Git Commands for Software Engineers
A guide to common Git commands for configuring repositories, tracking changes, managing branches, working with remotes, and handling history, stashes, tags, and patches.
10 new Git commands you should start using today
A round-up of ten Git commands added since version 2.23 that replace overloaded old ones, automate repo maintenance, and make merges, rebases and monorepos easier to handle.
7 practices to follow for a successful code handover
The note lists seven handover practices: keep everything in version control, secure management support, have new developers write documentation, use tests to learn the system, and avoid goal-less refactoring.
5 reasons why Git based resume is awesome
The author argues that keeping a resume in GitHub makes it portable, easier to review through pull requests, simpler to customize, cheaper to manage, and free from dependence on a fixed document stack.
Trunk-based Development vs. Git Flow
The article compares Git flow and trunk-based development, showing how each workflow shapes branching, review, speed, and control, and when each fits open source, junior teams, startups, or senior teams.
Here are all the Git commands I used last week, and what they do.
The page lists common Git commands for initializing, cloning, branching, merging, pulling, inspecting changes, and reviewing history, then adds cautions about force pushes, rebasing, and commit message cleanup.
Getting Git
A comprehensive video series that takes viewers from `git init` to Git Master, with PayPal payment available by sending money to jmac@gettinggit.com.
How to master the art of Git
The article explains what Git is, how GitHub fits in, and the basic workflow of cloning, checking status, staging, committing, pushing, pulling, and reverting changes.
When to make a Git Commit
The post says to commit when you finish a unit of work or when you have changes you may want to undo. It argues that units of work should be defined by feature, not by time or file type.
Oh shit, git!
The page collects plain-English fixes for common Git messes, including reflog recovery, amending commits, moving commits to the right branch, checking staged diffs, and starting over by recloning.
One Commit. One Change.
The post argues that commits should be atomic: one change only, so they can be reverted cleanly, keep builds consistent, and make history easier to trace.
Learn Enough Git to Be Dangerous
Introduces Git as the version-control tool in the Learn Enough fundamentals trilogy, then walks through setup, commits, diffs, branching, merging, collaboration, and GitHub Pages.
8 Small git tips
The post collects eight practical Git tips: partial staging, interactive rebase, stashing, a global ignore file, whitespace warnings, autosetuprebase, clearer logs, and amending commit messages.
Jogar Pedra em Gato Morto: por que Subversion não presta
O texto defende que Subversion foi útil, mas já passou da hora de mudar para um VCS distribuído, sobretudo GIT, porque branches e merges continuam difíceis e tediosos.
What Makes a Good Check-in?
The article argues that a good check-in should have one intent, a tight scope, a clear description, build and test consistency, completeness, review, traceability, and reversibility.