gulp plugin to publish contents to Github pages
npm install --save-dev gulp-gh-pages
Define a deploy
task in your gulpfile.js
(as below) which can be used to push to gh-pages
going forward.
var gulp = require('gulp');
var ghPages = require('gulp-gh-pages');
gulp.task('deploy', function() {
return gulp.src('./dist/**/*')
.pipe(ghPages());
});
Now, you should be able to call your task by doing:
gulp deploy
var ghPages = require('gulp-gh-pages');
options: Object
Return: Object
(stream.Transform)
Type: String
Default: URL for the remote of the current dir (assumes a git repository)
By default gulp-gh-pages
assumes the current working directory is a git repository and uses its remote url. If your gulpfile.js
is not in a git repository, or if you want to push to a different remote url, you can specify it. Ensure you have write access to the repository.
Type: String
Default: "origin"
Git remote.
Type: String
Default: "gh-pages"
The branch where deploy will by done. Change to "master" for username.github.io
projects.
Type: String
Default: .publish
Set the directory path to keep a cache of the repository. If it doesn't exist, gulp-gh-pages automatically create it.
Type: Boolean
Default: true
Allow you to make a build on the defined branch without pushing it to master. Useful for dry run.
Type: Boolean
Default: false
Force adding files to the gh-pages
branch, even if they are ignored by .gitignore
or .gitignore_global
.
Type: String
Default: "Update [timestamp]"
Edit commit message.
Type: Boolean
Default: true
Allow you to override old files instead of removing and copying.
true
for remove and copy. false
for override.
Useful when you want to keep old builds.
Copyright (c) 2014 Micheal Benedict, 2015 Shinnosuke Watanabe
Licensed under the MIT License.