taproot-manufacturing/entomologist
2
0
Fork 0
Code Issues 1 Pull requests 2 Projects Releases Packages Wiki Activity Actions

Compare commits

base: taproot-manufacturing:4da0a0788db235c2dd1fb8eefd86a0a1c3e8066d
Branches Tags
taproot-manufacturing:main
taproot-manufacturing:entomologist-data
taproot-manufacturing:tags-dir
taproot-manufacturing:03/entries
taproot-manufacturing:03/tui
..
compare: taproot-manufacturing:32d4e105290446826a0081ccb4cbe7130f82672c
Branches Tags
taproot-manufacturing:entomologist-data
taproot-manufacturing:tags-dir
taproot-manufacturing:main
taproot-manufacturing:03/entries
taproot-manufacturing:03/tui

No commits in common. "4da0a0788db235c2dd1fb8eefd86a0a1c3e8066d" and "32d4e105290446826a0081ccb4cbe7130f82672c" have entirely different histories.
4da0a0788d ... 32d4e10529

1 changed files with 0 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

15
e089400e8a9e11fe9bf10d50b2f889d7/description
View file

@ -1,15 +0,0 @@
keep local `entomologist-data` branch in sync with `origin/entomologist-data`
My git workflow does not use `git pull`, instead i:
1. `git fetch`
2. `git merge` or `git rebase`
When i run `git fetch` to fetch new issues, my local
`entomologist-data` branch does not get automatically synchronized with
`origin/entomologist-data`.
The clumsy workaround is:
1. `git fetch`
2. `git checkout entomologist-data`
3. `git merge origin/entomologist-data`
4. `git checkout ${BRANCH}`