Skip to content

Commit 7d126e4

Browse files
committed
Add link to template guide for ease of ref
1 parent e02b10d commit 7d126e4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/wiki-guide/Git-Cherry-Pick-Guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Git Cherry-pick update for Downstream Repos
22

3-
`git cherry-pick` is a handy tool to directly apply specific commits from one branch or repo to another even when they don't share a git history—especially when you do not want to merge large change sets. This can be helpful when forking another repo or building off an evolving template, such as the Collaborative Distributed Science Guide. Below, we provide a step-by-step guide to updating repositories based on updating this repo from the template guide:
3+
`git cherry-pick` is a handy tool to directly apply specific commits from one branch or repo to another even when they don't share a git history—especially when you do not want to merge large change sets. This can be helpful when forking another repo or building off an evolving template, such as the [Collaborative Distributed Science Guide](https://github.com/Imageomics/Collaborative-distributed-science-guide). Below, we provide a step-by-step guide to updating repositories based on updating this repo from the template guide:
44

55
!!! tip "Be Prepared!"
66
Before you start, you should know which commits are going to be pulled from the template repo. Collect their hashes in a separate text file; be sure to list them in chronological order, so they can be applied correctly.

0 commit comments

Comments
 (0)