Closed kan-fu closed 9 months ago
Huh, never knew commit conventions were a thing. Good to know.
Huh, never knew commit conventions were a thing. Good to know.
The idea first came to me when I read the py-pkgs book. Although it is mainly used together with Python Semantic Release library, which is too much for this repo, I believe adding some quick types in the commit message will definitely help when writing the release notes.
Huh, never knew commit conventions were a thing. Good to know.
The idea first came to me when I read the py-pkgs book. Although it is mainly used together with Python Semantic Release library, which is too much for this repo, I believe adding some quick types in the commit message will definitely help when writing the release notes.
These are neat. I had previously been using pandas commit message format, but I like the py-pkgs one.
Besides setting the minimum python version to 3.8, the latest commit updates some outdated text on Readme file, and move onc to src folder. Initially I did not plan to move the onc folder because [tool.setuptools] in pyproject.toml works fine. There are many libraries (like pandas and numpy) that has this non-src layout.
However I met some problems when using sphinx-autoapi extension. Using src layout magically solves the issue. Also I am persuaded by py-pkg and setuptools documentations.
I've had both /src/ and flat layouts before. Usually there's something in conf.py with sphinx. This is a common bikeshedding issue, so go with whatever works.
Are you looking for an additional review on this PR? This LGTM
Partly fix #1. DMAS-77309. I will have another PR to add CI after this PR is merged since it already contains several commits.
Suggest to review each commit separately because the commit that adds formatter can be safely ignored.
There are three steps:
BTW, I am following Angular Commit Style for the commit messages. It is described at here and here.