Branches and Merges¶
Branches¶
A branch is a movable pointer to a line of work. Use branches to isolate changes before they become part of main.
Common branch names:
notes/ssh-hardeninglab/nmap-baselinefix/broken-linkincident/timeline-draft
Merge¶
After work is reviewed or ready:
Conflicts¶
A conflict happens when Git cannot automatically combine changes. Resolve it by:
- Opening the conflicted file.
- Choosing the correct final content.
- Removing conflict markers.
- Staging and committing the resolution.
Note
In security documentation, preserve evidence chronology. Do not "clean up" a conflict by deleting useful investigation notes unless you are sure they are duplicated elsewhere.