We welcome any contributions to Tina, whether it be bug reports, feature requests, or code contributions. Please read the Code of Conduct before contributing.
- Submit your PR to the
devbranch. Do not submit PRs to themainbranch. - Complete the PR checklist.
- Ensure you are following the Code of Conduct at all times.
- Await a review from a Tina maintainer or general user, as you see fit.
Your code will be merged into the dev branch once it has been reviewed, approved, and tested by a Tina maintainer.
We use Conventional Commits for our commit messages.
When pair-programming or working on something with the help of somebody else, please add them as a Co-Author to your PR/commit, if simply out of the goodness of your heart.
Adding a new feature. Should be used when an external API is added as well.
feat: added network layer
Fixing an oversight (unreported bug).
fix: network tokenization
Fixing a bug.
bugfix: network tokenization layer
Refactoring code, such as renaming variables, etc.
refactor: ugly network layer
Minor/Major optimizations that don't count as refactors.
speed: network layer string.byte
Fixing style issues, such as linting, formatting, etc.
style: eslint fix
Anything repository/workflow related.
meta: add issue template