Skip to content

Latest commit

 

History

History
56 lines (38 loc) · 2.73 KB

CONTRIBUTING.md

File metadata and controls

56 lines (38 loc) · 2.73 KB
Raw

What do I need to know to help?

When contributing to this repository, please feel free to discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

What can you contribute?

There are numerous ways to contribute to this project, like providing solutions with explanations, fixing any errors, adding missing information, codes, links to online answers for any of the problems, and so on.

How do I make a contribution?

If you've never made an open source contribution before or you are wondering how contributions work in our project? Here's a quick rundown!

  1. Fork the repository to your account. This means that you will have a copy of the repository under <your-GitHub-username>/<repository-name>.

  2. Clone the repository to your local machine using by copying the link provided under HTTPS when you click on the green button labeled code on the repository page

    $ git clone https://github.com/<your-GitHub-username>/JPMC-Quant-Challenge-2022

  3. Create a new branch for your changes or fix

     $ git checkout -b <branch-name>

  4. Setup the project in your local by following the steps listed in the README.md file.

  5. Open the project in a code editor and begin working on it.

  6. Add the contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index

    $ git add .

  7. Add a descriptive commit message

    $ git commit -m "Insert a short message of the changes made here"

  8. Push the changes to the remote repository

    $ git push -u origin <branch-name>

  9. Submit a pull request to the upstream repository.

  10. Title the pull request with a short description of the changes you made and request a review from a maintainer/reviewer. For example, you can title an issue like so "Added New Derivative Modelling Questions". In the description of the pull request, be sure to explain the changes that you made and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!

  11. Wait for the pull request to be reviewed by a maintainer.

  12. Make changes to the pull request if the reviewing maintainer recommends them.

  13. Celebrate your success after your pull request is merged! 🎉

Reviewer/Maintainers

GitHub: Aaryan Arora
Email: [email protected]
Linkedin: https://www.linkedin.com/in/aaryan-arora-a956b8203/