While going through the repo I noticed the project's own host-side Python (notably create-envfile.py) has no tests, and there's a .flake8 config that isn't run by any workflow.
I'd like to propose, only if it fits how you want this template maintained:
- A small
pytest suite for create-envfile.py covering its real branches — JSON-vs-CLI precedence, the https-requires-email guard, env_type → debug / letsencrypt_mode, and full {placeholder} substitution.
- A minimal GitHub Actions workflow that runs flake8 (using the existing
.flake8) and those tests on push/PR.
Both would be small and kept separate (one concern per PR). Before writing anything: is a test + CI layer something you'd welcome here, or do you deliberately keep this repo's CI minimal since it tracks GeoNode master? Happy to follow whatever direction you prefer.
While going through the repo I noticed the project's own host-side Python (notably
create-envfile.py) has no tests, and there's a.flake8config that isn't run by any workflow.I'd like to propose, only if it fits how you want this template maintained:
pytestsuite forcreate-envfile.pycovering its real branches — JSON-vs-CLI precedence, the https-requires-email guard,env_type→debug/letsencrypt_mode, and full{placeholder}substitution..flake8) and those tests on push/PR.Both would be small and kept separate (one concern per PR). Before writing anything: is a test + CI layer something you'd welcome here, or do you deliberately keep this repo's CI minimal since it tracks GeoNode master? Happy to follow whatever direction you prefer.