We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In mochajs/mocha#2621, the automated message contains the following:
There are at least two problems here:
My working copy's origin is not github.com/mochajs/mocha, it's github.com/boneskull/mocha.
origin
github.com/mochajs/mocha
github.com/boneskull/mocha
I believe you can get away with just giving git the URL:
$ git push ssh://git@github.com/mochajs/mocha.git greenkeeper/update-all
I don't know if it's better to use an https scheme.
https
git fetch assumes origin. Again, a specific URL, or git fetch --all may be better.
git fetch
git fetch --all
I realize it isn't really Greenkeeper's job to teach developers how to use git. Either way, had I followed these instructions, it wouldn't work.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
In mochajs/mocha#2621, the automated message contains the following:
There are at least two problems here:
My working copy's
origin
is notgithub.com/mochajs/mocha
, it'sgithub.com/boneskull/mocha
.I believe you can get away with just giving git the URL:
I don't know if it's better to use an
https
scheme.git fetch
assumesorigin
. Again, a specific URL, orgit fetch --all
may be better.I realize it isn't really Greenkeeper's job to teach developers how to use git. Either way, had I followed these instructions, it wouldn't work.
The text was updated successfully, but these errors were encountered: