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
Issue 250: Ground work to shift development to main
from develop
#256
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #256 +/- ##
========================================
Coverage 96.82% 96.82%
========================================
Files 15 15
Lines 1574 1574
========================================
Hits 1524 1524
Misses 50 50 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine except: something to fix with the renderer?
A few other asides in comments; take 'em or leave 'em.
Co-authored-by: Hugo Gruson <Bisaloo@users.noreply.github.com>
Co-authored-by: Carl A. B. Pearson <pearsonca@users.noreply.github.com>
Description
This PR closes #250.
As discussed in #250 there are a range of benefits to shifting development to
main
with the key benefits of usingdevelop
having been eroded by enabling release-only building on R-universe. This PR updates the README and contributing guide to drop mentions ofdevelop
and make distinctions clear between the various available package versions.It also:
README.Rmd
when it is touched.This PR does not remove the
develop
triggers in our CI as this would break the current development workflow and does not remove thedevelop
branch as we are still using it for this minor release.Checklist
NEWS.md
and theDESCRIPTION
.