ESCOMP / ESCOMP/CTSM-LUH-LandUseDataPrepTools
A few repository things to think through
- Dominant language
- C
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
@lawrencepj1 I'm just going to list a few repository workflow type things to think through. We probably just talk about this at one of the next pft/landuse tools meetings.
- [x] Who are the likely people to work here? How often are changes likely to happen?
- [x] Are there any considerations for when we include this as a submodule in CTSM?
- [x] Think about the tag naming convention
- [x] What the Commit/PR/tag workflow process should look like?
- [x] Do we put in place any restrictions on who can bring in changes?
- [x] Do we put in place any restrictions on the main branch? Or other branches?
- [x] What kind of testing can/should be added?
- [x] Is there any automated checking or testing that could be added?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.