Any contribution is appreciated! You might want to:
- Fix spelling errors
- Improve documentation
- Add tests for untested code
- Add new features
- Fix bugs
- Use issues to report bugs and features
- If you report a bug in the results for a particular OneNote, include that .one. This allows others to replicate the issue.
- Fix issues by creating pull requests.
- Help others by sharing your thoughs in comments on issues and pull requests.
- Search previous issues, as yours might be a duplicate.
- When creating a new issue for a bug, include a minimal reproducible example.
- When creating a new issue for a feature, be sure to describe the context of the problem you are trying to solve. This will help others to see the importance of your feature request.
- A pull request should close an existing issue. For example, use "Fix #123" to indicate that your PR fixes issue 123.
- Pull requests should be merged to master.
- Include unit tests when possible. In case of bugs, this will help to prevent the same mistake in the future. In case of features, this will show that your code works correctly.
- Code should work for Python 3.11+.
- Test your code.
- New features should be well documented using docstrings.
- Check if the README.md documentation needs to be updated.
- Check spelling and grammar.
In order to get a clear contribution chain of trust we use the signed-of-by language used by the Linux kernel project. Please make sure your commit message adheres to this guideline.
- This package is distributed under the MIT license.
- All dependencies should be compatible with this license.
- Use licensecheck to validate if new packages are compatible.
-
Clone the repository
git clone https://github.com/hbrns/onenote-to-tana.git cd onenote_to-tana -
Install dev dependencies
poetry install --with=dev
-
Run the tests
cd onenote_to-tana python convert_to_tif.py --help