From 5280c192c8a833f5d3ed6089248270d211f6c28f Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 24 Dec 2025 05:37:29 +0000 Subject: [PATCH 1/2] Initial plan From 30bf5b1f502908ab6b519f2e8764deadcfc68192 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 24 Dec 2025 05:40:06 +0000 Subject: [PATCH 2/2] Add contribution guidelines with bug fix and feature request requirements Co-authored-by: Fila91bot <208684497+Fila91bot@users.noreply.github.com> --- CONTRIBUTING.md | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ README.md | 6 +++++- 2 files changed, 53 insertions(+), 1 deletion(-) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..5667ad1 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,48 @@ +# Contributing to novi-tokeni + +Thank you for your interest in contributing to novi-tokeni! We appreciate your help in making this project better. + +## How to Contribute + +### Reporting Bugs + +If you find a bug, please create an issue with the following information: +- A clear and descriptive title +- Steps to reproduce the bug +- Expected behavior +- Actual behavior +- Any relevant logs or screenshots + +### Fixing Bugs + +If you are fixing a bug: +1. **Reference the issue number** in your pull request description +2. Fork the repository +3. Create a new branch for your fix +4. Make your changes +5. Test your changes +6. Submit a pull request with a clear description of the fix + +### Implementing Features + +If you are implementing a feature request: +1. **Check with the maintainers first** that the feature will be accepted +2. Create or reference an existing issue describing the feature +3. Wait for maintainer approval before starting work +4. Fork the repository +5. Create a new branch for your feature +6. Implement the feature +7. Test your changes +8. Submit a pull request with a clear description + +## Pull Request Guidelines + +- Keep pull requests focused on a single issue or feature +- Write clear, descriptive commit messages +- Reference any related issues in your PR description +- Ensure your code follows the existing code style +- Test your changes before submitting + +## Questions? + +If you have questions about contributing, please open an issue and we'll be happy to help! diff --git a/README.md b/README.md index 4af1b00..b7c2c1b 100644 --- a/README.md +++ b/README.md @@ -1 +1,5 @@ -# novi-tokeni \ No newline at end of file +# novi-tokeni + +## Contributing + +We welcome contributions! Please see our [Contributing Guidelines](CONTRIBUTING.md) for details on how to get started. \ No newline at end of file