Clarify why we use a separate pages branch
This commit is contained in:
parent
99ff0c2425
commit
2e004ac918
@ -4,8 +4,12 @@
|
|||||||
|
|
||||||
Example [GitBook] website using GitLab Pages.
|
Example [GitBook] website using GitLab Pages.
|
||||||
|
|
||||||
This project uses an orphan branch (`pages`) to host the book.
|
This project uses an orphan branch (`pages`) to host the book, since GitBook
|
||||||
This way, you can have your project's code in the `master` branch and use `pages` for accommodating only your website content.
|
[expects a README.md](http://toolchain.gitbook.com/structure.html) file present
|
||||||
|
in the root directory, and we already use one in the `master` branch to provide
|
||||||
|
information about GitBook on GitLab Pages. That way, you can have your project's
|
||||||
|
code in the `master` branch and use `pages` for accommodating only your website
|
||||||
|
content.
|
||||||
|
|
||||||
Learn more about GitLab Pages at https://pages.gitlab.io and the official
|
Learn more about GitLab Pages at https://pages.gitlab.io and the official
|
||||||
documentation http://doc.gitlab.com/ee/pages/README.html.
|
documentation http://doc.gitlab.com/ee/pages/README.html.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user