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: CHANGELOG.md
+6
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,9 @@
1
+
# v1.0.0-beta.1
2
+
## Deploy to root on `master` branch
3
+
4
+
- when branch is `master`, the directory won't be deployed to `/branch/${branchName}`, but `/` instead, allowing consumers to only rely on this package and not need `gh-pages` in addition
A Node and CLI tool that makes deploying a directory on a branch to GitHub pages easy and automatic,
9
-
to help your peers QA your built docs/demos easily for better feedback.
8
+
A Node and CLI tool that makes deploying to GitHub pages **by branch** easy and automatic, best used as part of a CI process.
9
+
10
+
On `master`, your directory will be deployed to your GitHub page root similarly to other libraries, such as the wonderful [`gh-pages`](https://www.npmjs.com/package/gh-pages).
11
+
On other branches, it'll be deployed under `/branch/${branchName}`, allowing your peers to QA your built docs/demos easily for better feedback.
10
12
11
13
It also sends a status to a Pull request, if one exists:
|`buildUrl`| -u | link displayed when deployment fails |||||
47
49
48
50
Therefore, if ran from CircleCI with a `GITHUB_TOKEN` environment variable present and the directory to be deployed is named `public`, _no configuration options are needed_, so just the following is enough:
0 commit comments