The Trans Directory
docs: make setting upstream more clear, docs on npx quartz restore
+9
+6
content/migrating from Quartz 3.md
+6
content/migrating from Quartz 3.md
···
12
12
npx quartz create
13
13
```
14
14
15
+
If you get an error like `fatal: 'upstream' does not appear to be a git repository`, make sure you add `upstream` as a remote origin:
16
+
17
+
```shell
18
+
git remote add upstream https://github.com/jackyzha0/quartz.git
19
+
```
20
+
15
21
When running `npx quartz create`, you will be prompted as to how to initialize your content folder. Here, you can choose to import or link your previous content folder and Quartz should work just as you expect it to.
16
22
17
23
> [!note]
+3
content/upgrading.md
+3
content/upgrading.md
···
13
13
14
14
As Quartz uses [git](https://git-scm.com/) under the hood for versioning, updating effectively 'pulls' in the updates from the official Quartz GitHub repository. If you have local changes that might conflict with the updates, you may need to resolve these manually yourself (or, pull manually using `git pull origin upstream`).
15
15
16
+
> [!hint]
17
+
> Quartz will try to cache your content before updating to try and prevent merge conflicts. If you get a conflict mid-merge, you can stop the merge and then run `npx quartz restore` to restore your content from the cache.
18
+
16
19
If you have the [GitHub desktop app](https://desktop.github.com/), this will automatically open to help you resolve the conflicts. Otherwise, you will need to resolve this in a text editor like VSCode. For more help on resolving conflicts manually, check out the [GitHub guide on resolving merge conflicts](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line#competing-line-change-merge-conflicts).