Skip to content

Latest commit

 

History

History
71 lines (45 loc) · 2.59 KB

CONTRIBUTING.md

File metadata and controls

71 lines (45 loc) · 2.59 KB

Contributing to Impact-Wall

First of all, thank you for considering contributing to Impact-Wall!

The following is a set of guidelines for contributing to Impact-Wall. Please take a moment to review this document to ensure that your contributions align with the project's standards.

Table of Contents

  1. Code of Conduct
  2. How Can I Contribute?
  3. Development Setup
  4. Commit Message Guidelines
  5. Pull Request Process
  6. Code of Conduct
  7. License

How Can I Contribute?

Reporting Bugs

If you encounter a bug, please create an issue on the GitHub repository. When creating an issue, provide as much detail as possible, including your operating system, relevant environment details, and a clear description of the issue.

Suggesting Enhancements

Your ideas and suggestions are welcome! If you have an enhancement in mind, please open an issue with the "enhancement" label.

Code Contributions

We welcome code contributions through pull requests. To contribute code:

  1. Fork the repository.
  2. Create a new branch with a descriptive name (git checkout -b feature-name).
  3. Make your changes.
  4. Test your changes thoroughly.
  5. Commit your changes with clear and concise commit messages.
  6. Push your changes to your fork (git push origin feature-name).
  7. Create a pull request.

We appreciate your effort and will review your contribution as soon as possible.

Development Setup

To set up the development environment, follow these steps:

  1. Clone the repository: git clone https://github.com/maida12/Impact-Wall.git.

Commit Message Guidelines

Please follow the conventional commit message format. This helps us automate the release process and generate a meaningful changelog. Each commit message should have a clear and concise description of the changes.

Pull Request Process

  1. Ensure your pull request is linked to an existing issue (if applicable).
  2. Provide a clear description of your changes.
  3. Ensure that your code follows the project's coding standards.
  4. Test your changes locally.
  5. Squash your commits into a single commit with a descriptive message.
  6. Request reviews from maintainers.
  7. Once your pull request is approved, it will be merged.

Code of Conduct

Please follow our Code of Conduct in all interactions.

Thank you for your contributions!