Closed sckott closed 7 years ago
Hi Scott,
Great idea, I'll do this from now on.
Tom
@AugustT any chance you can start doing this? when I put out ropensci news i have no idea what new features/changes/bug fixes, etc, - Same for your users :)
Okay, I have most of this in place now. However, the tags I have added to my repo don't seem to pull across into this repo? Do you know how to make that work?
Looking at your version, you don't have any tags. Am I missing something?
It seems tag changes behave in a slightly different way to code changes. Perhaps I need to push them directly to this repo?
Got it! PR does not pull tags. I needed to do
git push upstream --tags
oh, i was looking at https://github.com/JNCC-UK/rnbn since this repo says its forked from there
nice, i see you got it
Right, I think this is all in place... have I avoided getting coal for Christmas? ;) Let me know if there is anything I have missed.
i think it's good now. whenever I see a new version of an ropensci package, I look in https://github.com/ropensci/rnbn/releases for what has changed, so this is very helpful
hey @AugustT we want all ropensci pkgs to consistently keep track of changes, following https://github.com/ropensci/onboarding/blob/master/packaging_guide.md#-news
NEWS
orNEWS.md
file to keep track of changes with each version released to CRANCan you please do the three above items from now on?