Contribution Guidelines - Kriaa89/VivaFit GitHub Wiki

Contribution Guidelines

Welcome to the VivaFit project! We greatly appreciate your interest in contributing to our codebase, documentation, and overall project improvement. This document outlines the guidelines and processes for contributing in a clear and friendly manner.


🤝 How to Contribute

1. Reporting Issues

  • Submit an Issue:
    If you encounter any bugs or have suggestions for improvement, please open an issue in our repository. Be sure to include detailed steps to reproduce the problem and any other relevant information.

2. Proposing Features

  • Feature Request:
    New feature requests are welcome! Please open an issue tagged with “enhancement” and describe the proposed functionality, value, and any design suggestions.

3. Creating Pull Requests (PRs)

  • Fork the Repository:
    Create your own fork and work on a separate branch.
  • Follow the Coding Style:
    Adhere to our code style guidelines and best practices.
  • Commit Messages:
    Write clear, concise commit messages that describe your changes.
  • Submit a PR:
    Once your changes are ready, submit a PR describing what you’ve done, referencing any associated issues.

4. Documentation & Wiki


🛠️ Development Workflow

flowchart TD
    A[Open an Issue or Feature Request] --> B[Fork the Repository]
    B --> C[Create a New Branch]
    C --> D[Make Your Changes]
    D --> E[Commit and Push Changes]
    E --> F[Open a Pull Request]
    F --> G[Review & Feedback]
    G --> H[PR Merged into Main Branch]

📜 Code of Conduct

We expect everyone to follow our Code of Conduct. Treat everyone with respect and collaborate in a positive and constructive manner.


📌 Additional Resources


We thank you for your contributions to VivaFit. Your support and dedication help us build a better product for everyone!