Skip to content

Latest commit

 

History

History
107 lines (81 loc) · 4.51 KB

CONTRIBUTING.md

File metadata and controls

107 lines (81 loc) · 4.51 KB
Raw

Contributing Guidelines

Welcome to the project! We appreciate your interest and contributions. Before getting started, please take a moment to review the following guidelines.

Technology Stack

Table of Contents

How Can You Contribute

There are several ways you can contribute to this project:

Reporting bugs and issues:

Identifying and reporting bugs is one of the most helpful ways you can contribute. If you encounter any problems or unexpected behavior while using the project, please let us know.

Requesting new features

If you have an idea for a new feature that could enhance the project, we'd love to hear it. Submit a feature request detailing how the feature would work and why it would be beneficial.

Fixing bugs and implementing new features

Contributing code is a fantastic way to improve the project. You can help by fixing existing bugs or implementing new features. Ensure your contributions adhere to our coding standards and best practices.

Improving documentation and enhancing it

Clear and comprehensive documentation is crucial. You can contribute by correcting errors, adding explanations, or creating new documentation to help users and developers understand the project better.

Providing feedback and suggestions

Your feedback and suggestions are invaluable. They help us understand user needs and improve the project. Whether it's a comment on an existing feature or a suggestion for a new one, we welcome your input.

Code Contribution

If you would like to contribute code to the project, please follow these steps:

  • Step 1: Fork the repo first

  • Step 2: Go to your Git terminal and clone it on your machine.

    git clone https://github.com/<your_github_username>/UMatter.git

  • Step 3: Add an upstream link to the main branch in your cloned repo

    git remote add upstream https://github.com/MonalikaPatnaik/UMatter.git

  • Step 4: Keep your cloned repository up to date by pulling from upstream. This will help you avoid merge conflicts while committing new changes.

    git pull upstream main

  • Step 5: Create your feature branch (This is a necessary step, so don't skip it)

    git checkout -b <feature-name>

  • Step 6: Track and stage your changes.

     # Track the changes
 git status

 # Add changes to Index
 git add . or git add <file_name>

  • Step 7: Commit your changes (Write commit message as "Small Message")

    git commit -m "Write a meaningful but small commit message"

  • Step 8: Push the changes for review

    git push -u origin <branch-name>

  • Step 9: Create a pull request on GitHub. (Don't just hit the create a pull request button; you must write a PR message to clarify why and what you are contributing).

Bug Reports

If you encounter any bugs or issues while using the project, please follow these steps:

  • Check if the issue has already been reported by searching the existing issues.
  • If the issue has not been reported, open a new issue.
  • Provide a clear and descriptive title for the issue.
  • Include steps to reproduce the issue.
  • Describe the expected behavior and the actual behavior.
  • Provide any relevant error messages or screenshots.

Feature Requests

If you have a feature request, please follow these steps:

  • Check if the feature has already been requested by searching the existing issues.
  • If the feature has not been requested, open a new issue.
  • Provide a clear and descriptive title for the feature request.
  • Describe the problem or use case that the feature would address.
  • Provide a clear description of the proposed solution or implementation.

Community Guidelines

When participating in discussions and contributing to the project, we kindly ask you to follow our community guidelines. These guidelines ensure a positive and inclusive environment for everyone involved. Please review the README.md file for more information

LICENSE

By contributing to this project, you agree that your contributions will be licensed under the LICENSE of the project.