Skip to content

Latest commit

 

History

History
237 lines (163 loc) · 8.43 KB

CONTRIBUTING.md

File metadata and controls

237 lines (163 loc) · 8.43 KB
Raw

Contributing Guidelines 🎯

Thank you for your interest in contributing to Rentalog.in! We welcome contributions from everyone, whether you're fixing bugs, suggesting new features, improving documentation, or helping with testing.


Code of Conduct 📖

Please read and follow our Code of Conduct.


Need Help with the Basics? 🤔

If you're new to Git and GitHub, no worries! Here are some useful resources:


Project Structure 📂

RENTALOG.IN--FRONTEND/
├── .github/                  # GitHub-related configurations such as workflows, issue templates, etc
│   
├── public/                   # All the images for the reference of the public are included here
│   
├── src/                      # All the components of the project are included here
│   
├── eslintrc.cjs              
│     
├── .gitignore                
│   
├── Code of Conduct.md        # Some rules for the contributors
│   
├── CONTRIBUTING.md           # Instructions for the contributors
│   
├── index.css                 # Main stylesheet file of the project
│   
├── index.html                # Main document / structure file of the project
│   
├── index.jsx                 # Main script file of the project
│   
├── LICENSE                   # A permission to do something
├──
├── package-lock.json
├──
├── package.json
├──           
├── postcss.config.js
├──
├── README.md                 # Some basic instructions about the project
├──
├── tailwind.config.js
├──
├── vite.config.js

Types of Contributions

Bug Reports If you find a bug, please open an issue in the Issues section. Include the following information:

  • While raising an issue please kindly choose the appropriate template according to your issue.
  • Steps to reproduce the bug.
  • Expected behavior.
  • Actual behavior.
  • Screenshots, if applicable.
  • Feature Requests

We welcome suggestions for new features! Please open an issue with the label Feature Request and describe:

  • The feature you'd like to see.
  • How it would improve the application.
  • Any relevant examples or use cases.

Documentation Improvements

If you notice any errors or areas for improvement in the documentation, feel free to submit a pull request with your changes. Clear and comprehensive documentation helps everyone!

Design Contributions

If you're interested in contributing to the design aspnect, please create mockups or suggest improvements for the user interface.

Resources

[GitHub Flow](https://guides.github.com/introduction/flow/)
[Markdown Guide](https://www.markdownguide.org/)
[React Documentation](https://legacy.reactjs.org/docs/getting-started.html)


First Pull Request ✨

  1. Star this repository Click on the top right corner marked as Stars at last.

  2. Fork this repository Click on the top right corner marked as Fork at second last.

  3. Clone the forked repository

git clone https://github.com/<your-github-username>/Rentalog.in--Frontend.git
  1. Navigate to the project directory
cd Rentalog.in--Frontend
  1. Create a new branch
git checkout -b <your_branch_name>
  1. To make changes
git add .
  1. Now to commit
git commit -m "add comment according to your changes or addition of features inside this"
  1. Push your local commits to the remote repository
git push -u origin <your_branch_name>

  1. Create a Pull Request

  2. Congratulations! 🎉 you've made your contribution


Alternatively, contribute using GitHub Desktop 🖥️

  1. Open GitHub Desktop: Launch GitHub Desktop and log in to your GitHub account if you haven't already.

  2. Clone the Repository:

  • If you haven't cloned the Project-Guidance repository yet, you can do so by clicking on the "File" menu and selecting "Clone Repository."
  • Choose the Project-Guidance repository from the list of repositories on GitHub and clone it to your local machine.

3.Switch to the Correct Branch:

  • Ensure you are on the branch that you want to submit a pull request for.
  • If you need to switch branches, you can do so by clicking on the "Current Branch" dropdown menu and selecting the desired branch.
  1. Make Changes:
  • Make your changes to the code or files in the repository using your preferred code editor.
  1. Commit Changes:
  • In GitHub Desktop, you'll see a list of the files you've changed. Check the box next to each file you want to include in the commit.
  • Enter a summary and description for your changes in the "Summary" and "Description" fields, respectively. Click the "Commit to " button to commit your changes to the local branch.
  1. Push Changes to GitHub:
  • After committing your changes, click the "Push origin" button in the top right corner of GitHub Desktop to push your changes to your forked repository on GitHub.
  1. Create a Pull Request:
  • Go to the GitHub website and navigate to your fork of the Project-Guidance repository.
  • You should see a button to "Compare & pull request" between your fork and the original repository. Click on it.
  1. Review and Submit:
  • On the pull request page, review your changes and add any additional information, such as a title and description, that you want to include with your pull request.
  • Once you're satisfied, click the "Create pull request" button to submit your pull request.
  1. Wait for Review: Your pull request will now be available for review by the project maintainers. They may provide feedback or ask for changes before merging your pull request into the main branch of the Project-Guidance repository.

For Help And Support 💬


Good Coding Practices 🧑‍💻

  1. Follow the Project's Code Style

    • Maintain consistency with the existing code style (indentation, spacing, comments).
    • Use meaningful and descriptive names for variables, functions, and classes.
    • Keep functions short and focused on a single task.
    • Avoid hardcoding values; instead, use constants or configuration files when possible.

  2. Write Clear and Concise Comments

    • Use comments to explain why you did something, not just what you did.
    • Avoid unnecessary comments that state the obvious.
    • Document complex logic and functions with brief explanations to help others understand your thought -process.

  3. Keep Code DRY (Don't Repeat Yourself)

    • Avoid duplicating code. Reuse functions, methods, and components whenever possible.
    • If you find yourself copying and pasting code, consider creating a new function or component.

  4. Write Tests

    • Write unit tests for your functions and components.
    • Ensure your tests cover both expected outcomes and edge cases.
    • Run tests locally before making a pull request to make sure your changes don’t introduce new bugs.

  5. Code Reviews and Feedback

    • Be open to receiving constructive feedback from other contributors.
    • Conduct code reviews for others and provide meaningful suggestions to improve the code.
    • Always refactor your code based on feedback to meet the project's standards.

Questions ❓

If you have any questions or need further assistance, feel free to reach out to the maintainers or join the discussions in the Discussions section.


Thank you for contributing 💗

We truly appreciate your time and effort to help improve our project. Feel free to reach out if you have any questions or need guidance. Happy coding! 🚀