Skip to content

Latest commit

 

History

History
48 lines (39 loc) · 2.94 KB

CONTRIBUTING.md

File metadata and controls

48 lines (39 loc) · 2.94 KB

Contributing to TUF

First off, thank you for considering contributing to TUF! It's people like you that make TUF such a great project.


  1. If you find any bug feel free to change it.

  1. If you find a better solution (optimal solution) which reduces time and space for a exsiting code, Please add a seperate file and for the solution. So that we can have different appoches to a same problem.

  1. for example if i already had (example.cpp) as a solution and if you dont find any bug in the code but have a better solution just add another file in the same directory name (example2.cpp)

How Can I Contribute?

Reporting Bugs

If you find a bug, please report it by opening a new issue. Before you create a new issue, please do a quick search to see if the issue has already been reported.

Suggesting Enhancements

If you have an idea to enhance the project, we would love to hear about it. Please open a new issue and describe your idea.

Submitting Pull Requests

  1. Fork the Repository: Click the "Fork" button at the top of this repository to create your own copy.
  2. Clone the Repository: Clone your fork to your local machine.
    git clone https://github.com/your-username/TUF.git
  3. Create a New Branch: Create a new branch for your changes.
    git checkout -b feature-branch
  4. Make Your Changes: Make the necessary changes in your local repository.
  5. Commit Your Changes: Commit your changes with a clear message.
    git commit -m "Description of your changes"
  6. Push Your Changes: Push your changes to your forked repository.
    git push origin feature-branch
  7. Open a Pull Request: Go to the original repository on GitHub and create a new pull request. Describe your changes and link any related issues.

Code Style and Guidelines

  • Follow the existing code style.
  • Write clear, concise commit messages.
  • Ensure your code passes existing tests and add new tests for your changes.