Skip to content
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

Remove branches which we do not use or want to see? #14

Closed
MichaelSchulzMETNO opened this issue Nov 24, 2020 · 5 comments
Closed

Remove branches which we do not use or want to see? #14

MichaelSchulzMETNO opened this issue Nov 24, 2020 · 5 comments
Labels

Comments

@MichaelSchulzMETNO
Copy link

Would it be possible to identify the banches which we are not using and remove them from the NorESMhub/cime fork?

@monsieuralok
Copy link

monsieuralok commented Aug 31, 2021

@MichaelSchulzMETNO @matsbn @tto061 @oyvindseland @huitang-earth I will remove following branches from cime. It would be nice if you can check once and if want to keep it up let me know. I will delete these following branches on 1st October 2021.

altuntas/MOM6_misomip
aws-tutorial
altuntas/MOM6_mct
cime4.2.3_cheyenne_port
cesm1_3_branch
gh-pages
cime5.6.16_pop2cism
theia_fix
jayeshkrishna/adios_support
dqwu/anlworkstation_pio1
dqwu/anlworkstation_pio2
rsdunlapiv/cmeps0.4branch
nems_integration
nems_integration_fixed
jgfouca/branch-for-acme-split-2019-11-15
global_workflow
fv3gfs_cime_build
fischer/izumi
maint-5.6
uturuncoglu/ufs_release
mvertens/refactor_dmodels_to_esmf
revert-3377-update_nuopc_esmf
mvertens/new_component_directories
mvertens/new_component_directories2
mvertens/new_component_directories3
master_cime

Branches we will maintain temporary (development branches) and long term (release code):
cime5.6.10_cesm2_1_rel_06-Nor
cime5.6.10_cesm2_1_rel_06-Nor-dev
NorESM_LandSItes_Platform
feature-hamocc-vsls
N2dev_port_from_CESM2.2.0
master (we will decide later how it should emerge?)
CAM5.6.10
cime5.8.32-Nor

@MichaelSchulzMETNO
Copy link
Author

Small suggestion: Could you also indicate which branches should be kept in the future?

@monsieuralok
Copy link

Small suggestion: Could you also indicate which branches should be kept in the future?

@MichaelSchulzMETNO I have put list of branches that we will maintain temporary or long term. But, it would need some discussion after cleaning up this repository. My present aim is to remove maximum unnecessary branches and then think about naming (as I discussed in last core meeting) and structures (I would soon discuss it in one core meeting).

@github-actions
Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Oct 25, 2023
@github-actions
Copy link

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants