Contributing to NuQuLib¶

Thank you for considering contributing to this package.

Feedbacks and contributions to NuQuLib are very welcome. These can be:

bug reports
submitting new functions or a patch to fix bugs
documentation issues
feature requests
etc.

For these contributions, it would be nice to let you know a basic policy (the workflow of code development and LICENSE, shown below) in this project.

Workflow of code development¶

If you are willing to contribute to this package, please keep in mind the following workflow.

We use the GitHub to host the package, to track issues/pull requests.
Please create a new branch for your work and make a pull request
- If you are not familiar with git, please refer to the Git documentation such as Git - Book.
- The main (default) branch of this repository is protected by ‘github branch protection’, so you cannot push directly to the main branch.
Consistent tests:

We use GitHub Actions to run the test codes and to build/deploy the document. When some changes are submitted through a pull request, the test codes (in pytest manner) are run to check that the changes are not destructive.

The test jobs are specified in yml files like .github/workflows/ci.yml and one can find the tests code in tests/ of the repository.

If you wish to add a new feature or to fix a bug, please consider to add a test code for it. All the classes and functions in the package should be accompanied by docstrings. Since we are using sphinx for documentation, please follow the docstring format used in the existing code or refer to the Sphinx documentation for guidance.
Managing the dependencies:

Please consider to use uv to manage the dependencies for development, and do not modify the pyproject.toml file directly. If you need to add a new dependency, please do it with uv add <package-name> and then commit the changes in pyproject.toml and uv.lock.

Since we are using GitHub Actions, only the allowed users can run the test jobs on GitHub Actions. If you are not an allowed user, please run the test codes locally before making a pull request with pytest.

How to test your changes locally¶

To test your changes locally before making a pull request, please follow these steps:

Clone the repository to your local machine if you haven’t already:
```
git clone https://github.com/SotaYoshida/nuqulib
```
Create a new branch for your changes:
```
git checkout -b your_branch
```
Make your changes to the codebase.
Install the required dependencies for testing. You can do this by running:
```
uv sync
```
Note that we assume you have uv installed and set up for this project. You can also try a virtual environment liks venv and pip if you prefer. However, the pip install -e . command can be not perfect to resolve the dependencies.
After installing the dependencies, you can activate your virtual environment:
```
source .venv/bin/activate
```
Run the test suite using pytest` to ensure that your changes do not break any existing functionality:
```
pytest -s tests/
```
If all tests pass, you can proceed to commit your changes and push your branch to GitHub for a pull request. Of course, you can also run specific test files or test cases as needed.
```
pytest -s tests/test_specific_file.py
```
If you are willing to check the coverage of your changes, you can use the following command:
```
pytest -v --cov=src/nuqulib/ -s --cov-report=html
```

LICENSE¶

Any contribution from you will be licensed under the same license as this project, which is MIT License.