-
Notifications
You must be signed in to change notification settings - Fork 0
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
For README.Rmd, maybe hard save the figures that won't be updated (when either of us commit they get updated but haven't changed). #44
Comments
And if you just kill the changes to figures (i.e. ignore that they've changed), you get this error:
The latter does override it, just a bit annoying to have to use. |
You should only get that if the .Rmd is newer than the .md. Look in .git/hooks/pre-commit if you want to disable that. The usethis package would have created it. |
…works (i.e. can commit newer README.Rmd than README.Md).
Thanks. Interesting. So much for telling people to "ignore the .git folder as you never need to touch it!". So, for the record, I removed
and could commit an edited README.Rmd that was newer than README.Md.
|
And to solve the original problem, we could maybe properly cache the figures and push them (need to look into exactly what happens now - we have fig.path and it doesn't remake figs every time, and then think about if this will fix the problem). Did a quick try of |
I just have the pre-commit.sample file. And I don't have that same text in my file as the one you deleted |
Thanks. Confusingly when I delete a .png file in man/figures, re-render the .Rmd, it creates the .png file again (with updated data), but still keeps the old timestamp of a month ago. I thought it might be doing something clever and the timestamp is to do with when the code chunk last changed (though I tried a test and that wasn't the case). I'll try removing the fig.path and add |
Solution - the reason we committed the figures is to not require the README.Rmd (which build on github) to download the bccm data, which takes time. So I will just hardwire those example figures in, and not commit the |
…ME-northhecatetemp-1.png) and check still builds fine on README on GitHub, #44.
Figured out a solution - working on it now..... |
Works for me and I think it should for Travis, and I added the pre-commit text back in. Travis you should probably do the same, i.e. have this code
as Then can close this. |
Today I get the original error again:
Thinking I should remove the corresponding line from the |
…EWS.md; had to remove four lines from pre-commit hook to not get git error again (#44, not pushed though).
Worked for me. Travis you will need to do the same at some point probably, i.e. remove
from |
Looks to be resolved, assuming Travis did the last bit locally. Not convinced it's completely needed. |
e.g. this commit 734b63 only added a badge (and updated the buoy number), but had lots of extraneous figures committed. Mention the workflow in Developers' Guidelines in README.
The text was updated successfully, but these errors were encountered: