Skip to content

Conversation

sarahkanee
Copy link

Description

Motivation and Context

Review Time Estimate

  • Immediately
  • Within one week
  • When possible

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My change requires a change to the documentation.
  • My name is in the list of CITATION.cff
  • I agree that PEcAn Project may distribute my contribution under any or all of
    • the same license as the existing code,
    • and/or the BSD 3-clause license.
  • I have updated the CHANGELOG.md.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@@ -0,0 +1,34 @@
#DAAC_Set_Credential(replace = TRUE)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest putting this in a subdirectory named magic, as done for the files in meta.analysis -- even though there's only one file here it should help us keep track of where things came from.

Even better but obviously more effort would be to add a short README to each subdirectory -- future viewers will be grateful for even a couple sentences explaining whose scripts they are, what project they were part of / how they're used, and how finished they are.

@dlebauer dlebauer added the ccmmf issues and pre related to the ccmmf project label Sep 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ccmmf issues and pre related to the ccmmf project Modules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants