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
{{ message }}
This repository has been archived by the owner on Oct 5, 2018. It is now read-only.
Right now, it's necessary to specify the repoUri explicitly. In most cases, however, the git repository for GitHub Pages is the same as the repository for the project. Therefore, it would be very convenient if the repoUri was set to the git property remote.origin.url by default.
Since there's currently no default, this change shouldn't break any existing users.
Right now, it's necessary to specify the repoUri explicitly. In most cases, however, the git repository for GitHub Pages is the same as the repository for the project. Therefore, it would be very convenient if the repoUri was set to the git property
remote.origin.url
by default.Since there's currently no default, this change shouldn't break any existing users.
The behavior I'm describing is how the gh-pages npm package, commonly used in Gulp builds. (See https://www.npmjs.com/package/gh-pages#optionsrepo).
In the meantime, I found a workaround using JGit directly. But it's not very elegant.
The text was updated successfully, but these errors were encountered: