Jimmy He
2024-01-01 002bbc37b140d177276cd655049e7de2072fa537
refs
author Jimmy He <417267+hhe@users.noreply.github.com>
Monday, January 1, 2024 22:14 +0000
committer GitHub <noreply@github.com>
Monday, January 1, 2024 22:14 +0000
commit002bbc37b140d177276cd655049e7de2072fa537
tree f321ebe31250d8a921de54aba5ce1f66c8b74353 tree | zip | gz
parent e603d7396b2eae90d1edb055e32fef33a5e77028 view | diff
fix: Continue setup even if a file to delete is not found (#663)

* Continue setup even if a file to delete is not found

For various reasons, `.gitkeep` may be deleted already.

(In my case, even though I followed the [Getting Started](https://quartz.jzhao.xyz) instructions exactly, my first run resulted in an `fatal: 'upstream' does not appear to be a git repository`)

If we try to delete `.gitkeep` again and don't ignore `ENOENT`, then the whole setup fails.

* Use fs.existsSync
1 files modified
5 ■■■■ changed files
quartz/cli/handlers.js 5 ●●●● diff | view | raw | blame | history