Skip to content

Merge develop into main#110

Draft
joewallwork wants to merge 215 commits intomainfrom
develop
Draft

Merge develop into main#110
joewallwork wants to merge 215 commits intomainfrom
develop

Conversation

@joewallwork
Copy link
Copy Markdown
Collaborator

@joewallwork joewallwork commented Mar 24, 2025

At the end of the project, once all open PRs have been merged or closed, we should merge the GISS-GC develop branch into the GISS-GC main branch.

Checklist

  • Check there are no open GEOS-Chem issues.
  • Check there are no open HEMCO issues.
  • Check any open GISS-GC issues are tasked as follow-ups to the project.
  • Merge GEOS-Chem develop into GEOS-Chem main (Merge GEOS-Chem develop into main geos-chem#17).
  • Merge HEMCO develop into HEMCO main (Merge HEMCO develop into main HEMCO#8).
  • Check all open GISS-GC PRs have been merged into develop or closed.
  • Check all open GEOS-Chem PRs have been merged into develop or closed.
  • Check all open HEMCO PRs have been merged into develop or closed.
  • Check .gitmodules specifies the main branches for each repo.
  • Check CI jobs pass for this PR.
  • Switch project settings back so that main is the default branch.

ltmurray and others added 30 commits July 19, 2024 16:33
…ompile and run as alternative chemistry operator and output subdaily mixing ratios diagnostics.
…date radiation code from F77 to F90 standard. Add some radiative forcing SUBDD diagnostics.
Tell git to ignore everything in the decks directory apart from the Makefile
Add `GISS_GC_14.R` rundeck to repo
…native chemistry operator.

These changes are likely robust.
This purposely breaks the GCClassic code, and is meant to try to get a working code, so we can go back to the prior commit with a new branch to create a version that preserves the existing GCClassic code.
@joewallwork joewallwork self-assigned this Mar 24, 2025
AdelekeBankole and others added 2 commits March 24, 2025 16:42
Use `develop` branch for all submodules
* remove outdated modelE README
* update readme with build instructions
* add contributing section to readme

Co-authored-by: Joe Wallwork <22053413+jwallwork23@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants