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
Copy file name to clipboardExpand all lines: src/publish/README.md
+2-12Lines changed: 2 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,19 +35,9 @@ A record of your previous publishes will be stored in a `_publish.yml` file with
35
35
36
36
Account information is not stored in this file, so it is suitable for checking in to version control and being shared by multiple publishers.
37
37
38
-
If you provide the `--id` option (described below) then a publish record is not saved (as in that case you already have another means for tracking published content).
39
-
40
-
## GitHub Pages
41
-
42
-
Publising to GitHub Pages works a little differently than to other providers. Rather than interacting with a remote API and writing publish records to `_publish.yml`, a special `gh-pages` branch is created and the contents of your `_site` or `_book` directory is pushed to this branch (GitHub will automatically publish a website when it sees a `gh-pages` branch created).
43
-
44
-
Ideally, `quarto publish` should be aware of the URL that will be used to access the published site (so that it can correctly write social metadata, a sitemap, and RSS feeds, all of which require absolute URLs). This URL can be deduced automatically for github.com but for GitHub Enterprise you should include a `site-url` in your website or book configuration. For example:
38
+
Note that GitHub Pages publishes are not stored in the `_publish.yml` file (they are tracked by virtue of the creation of a `gh-pages` branch).
If you provide the `--id` option (described below) then a publish record is not saved (as in that case you already have another means for tracking published content).
0 commit comments