Skip to content

Latest commit

 

History

History
75 lines (49 loc) · 1.85 KB

File metadata and controls

75 lines (49 loc) · 1.85 KB

Contributing Guidelines

Thank you for your interest in contributing to C Mini Projects! Any type of contribution — bug fixes, optimizations, or improvements — is truly appreciated. Every contribution, big or small, helps enhance this project!

Please read the guidelines below to ensure smooth and meaningful contributions.

How to Contribute

  1. Fork the repository

  2. Create a new branch

git checkout -b <feature-name>
  1. Make your changes

  2. Stage your changes

git add <your-changes>
  1. Commit your changes
git commit -m "Describe your changes here"
  1. Push the changes to your fork
git push origin <branch-name>
  1. Open a Pull Request

A good PR consists of:

  • A short, clear title
  • Explanation of what changed and why
  • Screenshots or logs (if your change affects output/visuals)

Pull Request Rules

To maintain quality and consistency across C Mini Projects:

  • Create an Issue first, and link it to your PR
  • Code must compile and run without errors or warnings
  • Remove unnecessary prints, unused variables, and dead code
  • Keep files clean, readable, and properly structured
  • Document any new feature or modification
  • Use meaningful variable/function names and consistent folder structure
  • Add comments wherever your logic might be unclear
  • Follow standard C formatting and indentation

Issue Guidelines

Before creating a new issue:

  • Check if an issue already exists
  • Provide a detailed description of the bug, idea, or enhancement
  • Include screenshots or error messages when possible
  • Suggest a possible fix (optional but helpful)

Testing Your Changes

Before submitting a pull request, double-check for finding any error.

Code of Conduct

Thank you! Your contributions help improve this project and support the open-source community. If you have any questions, feel free to reach out by opening an issue.