-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git.branch is not working #215
Comments
Indeed... I'll push a fix in the coming days. In the meantime, as a workaround, you can set the branch to use by modifying this file: |
@NGPixel thanks, but the npm package is still not upto date. I am using docker so i npm install the wiki. I assume most users do the same, rather than copying the source code |
@Bamieh Packages are no longer published to npm. See the docs for the new install method. The npm package (wiki.js) is simply calling these scripts from now on. I changed the CI flow recently and still have a few bug to fixes (hopefully by tomorrow), so your changes won't be included until this is fixed. If you're using docker, you can use the official image: https://docs.requarks.io/wiki/docker |
@NGPixel the docker image uses |
Are you using the latest docker image? npm install isn't used in the docker image... If you want to see how the image is built, you can check the wercker.yml file. |
I see, let me debug further into it then |
Actual behavior
in the
config.yml
adding the following does not do anythingExpected behavior
The wiki to sync with "content" branch
Steps to reproduce the behavior
change
git.branch
to any branch in the yml file.The wiki still pushes to master regardless. I tried
origin/content
aswell, same issue. The branch is created on github already, but it didnt work neither way. I am using ssh to authenticate githubThe text was updated successfully, but these errors were encountered: