Skip to content

Introduce pre-commit hooks and a package manager #11

@bojobo

Description

@bojobo

Per pre-commit:

Git hook scripts are useful for identifying simple issues before submission to code review. We run our hooks on every commit to automatically point out issues in code such as missing semicolons, trailing whitespace, and debug statements. By pointing these issues out before code review, this allows a code reviewer to focus on the architecture of a change while not wasting time with trivial style nitpicks.

For further development and contributions by others it makes sense to introduce the use of pre-commit hooks. They keep the code formatted and make sure that any contributor does not commit to main directly but rather to a different branch, which then can be merged if proven useful.

Similarly a package manager simplifies the setup for development, so that new contributors do not have to create a virtual environment by themselves but rather can simply execute the init command. I propose using uv. I find it easier to use than the competition and the speed is unmatched.

I have started this process and will create a PR as soon as I am done.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions