-
Notifications
You must be signed in to change notification settings - Fork 15
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
Clean up Dev branch #61
Comments
Branches ahead of dev
|
Looks like |
@kaydin I assume you want to leave the lab branches as a quick way to reference back to the version used in the class. Is there anything in them that should be merged into dev? |
@slucey yes I was going to suggest keeping the lab ones for reference, in case my class exercises stop working in future. I think I manually moved/cleaned up a few functions from the labs to dev that were globally useful, so nothing needed from the labs that isn't already in dev. |
eco_data is only ahead of dev because a new library version forced an update of RcppExports.cpp. Everything needed is merged into dev so safe to remove that one. Edit: confirmed eco_data branch safe to delete, and deleted it. |
@kaydin Great! Is there anything in |
Merging |
Merging via #68 |
Sorry thought I'd replied earlier - master_R4 was a temporary bridge between R versions 3 and 4 due to some library issues during that transition. Nothing here needed now. |
Lots of stale branches that need to be dealt with below is a list of branches and the date of their latest commit:
sense_alpha
lab_savepoint
lab_563_spring2020
(includes the previous two branches) 9/2/20master_R4
6/3/20adjust_vectors
6/17/21bioen
8/3/21gh-pages
10/13/21updateVignettes
12/6/21lab_563_Spring2022
4/25/22Last merge of dev to master 4/25/22
indiseas
6/8/22stanza_rollback
7/11/22Last dev commit 1/13/23
The text was updated successfully, but these errors were encountered: