Currently, there is no code formatter to ensure everything within the repository is standardize before each push to GitHub. The CI does not check for formatting consistenticies.
The use of black, a code formatting tool should be incorporated into the chiltepin environment, both for containers and for on-prem HPC systems so that users can conform to standardization for coding formatting before contributing to the repository.
Update --
The use of the black code formatter has been added to the Make lint CI step, however I can build this out into it's own step or rename this step altogether. For example, on the UW Team we have a make format step that runs both isort and black tooling together.
Currently, there is no code formatter to ensure everything within the repository is standardize before each push to GitHub. The CI does not check for formatting consistenticies.
The use of
black
, a code formatting tool should be incorporated into the chiltepin environment, both for containers and for on-prem HPC systems so that users can conform to standardization for coding formatting before contributing to the repository.Update -- The use of the
black
code formatter has been added to theMake lint
CI step, however I can build this out into it's own step or rename this step altogether. For example, on the UW Team we have amake format
step that runs bothisort
andblack
tooling together.Closes #64