Dotnet_Library/CONTRIBUTING.md

How to develop on this project

project_name welcomes contributions from the community.

You need Dotnet 9!

This instructions are for linux base systems. (Linux, MacOS, BSD, etc.)

Setting up your own fork of this repo.

• On gitea interface click on Fork button.
• Clone your fork of this repo. git clone git@git.disi.dev:YOUR_GIT_USERNAME/project_urlname.git
• Enter the directory cd project_urlname
• Add upstream repo git remote add upstream https://git.disi.dev/author_name/project_urlname

Run the tests to ensure everything is working

Run make test to run the tests.

Create a new branch to work on your contribution

Run git checkout -b my_contribution

Make your changes

Edit the files using your preferred editor. (we recommend VIM or VSCode)

Format the code

Run make fmt to format the code.

Lint the code

Run make lint to lint the code.

Test your changes

Run make test to run the tests.

Ensure code coverage report shows 100% coverage, add tests to your PR.

Build the docs locally

Run make docs to build the docs.

Ensure your new changes are documented.

Commit your changes

This project uses conventional git commit messages.

Example: fix(package): update setup.py arguments 🎉 (emojis are fine too)

Push your changes to your fork

Run git push origin my_contribution

Submit a pull request

On gitea interface, click on Pull Request button.

Wait CI to run and one of the developers will review your PR.

Makefile utilities

This project comes with a Makefile that contains a number of useful utility.

❯ make
Usage: make <target>

Targets:
help:             ## Show the help.
fmt:              ## Format code using black & isort.
test: lint        ## Run tests and generate coverage report.
clean:            ## Clean unused files.
release:          ## Create a new tag for release.
docs:             ## Build the documentation.

Making a new release

This project uses semantic versioning and tags releases with X.Y.Z Every time a new tag is created and pushed to the remote repo, gitea actions will automatically create a new release on gitea.

To trigger a new release all you need to do is.

1. If you have changes to add to the repo
   • Make your changes following the steps described above.
   • Commit your changes following the conventional git commit messages.
2. Run the tests to ensure everything is working.
3. Run make release to create a new tag and push it to the remote repo.

the make release will ask you the version number to create the tag, ex: type 0.1.1 when you are asked.

Caution

: The make release will change local changelog files and commit all the unstaged changes you have.