Skip to content

Latest commit

 

History

History
77 lines (45 loc) · 3.56 KB

CONTRIBUTING.md

File metadata and controls

77 lines (45 loc) · 3.56 KB
Raw

Contributing to Javascript-Interview-Preparation

Before getting started

👍🎉 First off, thank you so much for investing your time in contributing to our project! 🎉👍

The following is a set of guidelines for contributing to Javascript-Interview-Preparation. In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR. These are mostly guidelines, not rules.
Use your best judgment, and feel free to propose changes to this repository thorugh a pull request.

Please note we have a code of conduct, please follow it in all your interactions with the project to keep our community approachable and respectable.

Use the table of contents icon on the top left corner of this document to get to a specific section of this guide quickly.

How Can I Contribute?

If you have any javascript, react or web fundamentals related question which you think can be added to this repository, then you can always raise a pull request describing the question in detail & if possible providing a working solution of the question.

Pull requests are the best way to propose changes. We actively welcome your pull requests:

  1. Fork the repo and create your branch from master.
  2. If you've added new question, describe the question in detail & categorize it into repective folder (if present).
  3. If you've added a working solution to the question, describe your solution
  4. If possible attach an online editor link to the solution where maintainers can review it.
  5. Issue that pull request!

For further guidance about issuing a pull request, please refer to the below links:

Any contributions you make will be under the MIT Software License

In short, when you submit changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.

Report issues/bugs using GitHub's issues

We use GitHub issues to track public bugs or feature requests. Report a bug or request for a feature by opening a new issue; it's that easy!

Bug Reports

Great Bug Reports tend to have:

  • A quick summary and/or background
  • Steps to reproduce
    • Be specific!
    • Share the snapshot, if possible.
    • CodeSandbox live link
  • What actually happens
  • What you expected would happen
  • Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)

People love in-depth bug reports.

Feature Request

Great Feature Requests tend to have:

  • A quick idea summary
  • What & why you wanted to add the specific feature
  • Additional Context like images, links to resources to implement the feature etc.

For further guidance about creating a new issue, please refer to the related links:

Coding conventions

In order to sanitize coding standards, please follow this style guide.

License

By contributing, you agree that your contributions will be licensed under its MIT License.