You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 26, 2024. It is now read-only.
"The best way in my eyes is, to rebase because that fetches the latest changes of the upstream branch and replay your work on top of that." - [Stefan Bauer](https://stefanbauer.me/articles/how-to-keep-your-git-fork-up-to-date)
4
+
5
+
The ideal git history should have all Propeller modifications in a single most recent commit, followed by the full history from upstream CesiumGS.
6
+
7
+
e.g.
8
+
9
+
```
10
+
commit c6fc9cb205e387781c5269b95e350f61a8815d08
11
+
Author: Chris Cooper <chris@propelleraero.com>
12
+
Date: Mon Sep 21 15:19:02 2020 +1000
13
+
14
+
All the Propeller mods in a single commit
15
+
16
+
commit da4ddc58830606d89f762dc7d79b3dfe4103c6d1
17
+
Merge: 9c61508 6c0a0f8
18
+
Author: Kevin Ring <kevin@kotachrome.com>
19
+
Date: Tue Sep 1 15:47:38 2020 +1000
20
+
21
+
Updates for 1.73 release
22
+
23
+
...
24
+
```
25
+
26
+
To maintain this going forward, use a `git rebase`.
27
+
28
+
```
29
+
# Make sure your main branch is up to date
30
+
git checkout main
31
+
git pull
32
+
33
+
# Fetch the upstream tags
34
+
git fetch upstream --tags
35
+
36
+
# Interactive rebase to the CesiumGS release tag
37
+
# Squash all propeller commits into a single commit
38
+
git rebase -i 1.74
39
+
40
+
# Fix all the broken stuff :)
41
+
42
+
# You've just re-written the history so you'll have to force
0 commit comments