Add pre-commit hooks to the project by creating and then adding a .pre-commit-config.yaml file in a PR.

Additionally integrate https://pre-commit.ci/ with your GitHub account and enable it for this repository.

c.f. the pre-commit section in the Scientific Python Developer Guide for more information.

Even for test projects it is good practice to have some repository structure and defaults. GitHub helps you with this when creating a project by including options to generate a README, LICENSE, and .gitignore file at repository creation.

As a small exercise:

• Add a README to the project.
• Add a LICENSE to the project (https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository)
  • You can choose what LICENSE you want (c.f. https://choosealicense.com/) though selecting MIT if in doubt is probably fine.
• Add a Python .gitignore to the project (can just download and rename https://github.com/github/gitignore/blob/main/Python.gitignore)
• Move the project files under sk_b_c_example_swig/ to the top level directory to make it easier for a CI based workflow in the future

Do this in a typical PR based workflow and use a GitHub closing keyword to automatically close this Issue when the PR gets merged.

          As learning how to use cibuildwheel is a small task unto itself I would have kept the scope of this to just Issue #3 (so f6760e1804806b1caca408d819310ac38e38e116) and then built off of that in a seperate PR to add `cibuildwheel` support to build wheels that are distributable.

Originally posted by @matthewfeickert in #5 (comment)

In a PR add a GitHub Actions based workflow to the project that:

• builds an sdist and a wheel for the project on a ubuntu-latest runner
• also builds a wheel on macos-latest, and windows-latest runners
• Uses additional GitHub Actions to upload the sdist and wheels to GitHub as run artifacts.

To get started, read through the GitHub Actions: Intro guide that @henryiii wrote for Scientific Python and ask any questions that you have in this Issue. 👍

We'll just start with doing a simple build here (e.g. python -m build .), and then move to using cibuildwheel in a follow up PR.