-
Notifications
You must be signed in to change notification settings - Fork 24
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
Pull requests #260
Pull requests #260
Conversation
…into pull_requests
@DylanCarbone Why is appveyor still running? I'm happy to merge this, even with the minor lme4 installation bug on the old Ubuntu release, do you agree? |
@AugustT, that is odd. Please see this issue here. If this is correct, the appveyor failure is actually a log of a previous failure when the appveyor yml existed. The solution they suggest is to commit directly to the repo instead of merging a pull request. This could explain why there is no such issue in the BRCindicators repo, after you made a direct edit to the read me during our last meeting. Could you please try editing the readme file and pushing directly to the repo? Thanks |
I'm happy for you to merge, even with the lme4 installation bug. Strangely, that error hasn't occurred in my branch. It must be another random installation error. |
Okay I have removed the 'webhooks' for Appveyor which should solve that issue |
Hi @AugustT
Key changes:
mockery::stub()
function with thetestthat::with_mocked_bindings()
which does not alter global function configurations.Thanks,
Dylan