Skip to content

Latest commit

 

History

History
72 lines (52 loc) · 2.81 KB

contributing.md

File metadata and controls

72 lines (52 loc) · 2.81 KB

Contributing to Hedging-of-Financial-Derivative

Thank you for considering contributing to our Financial Derivative Hedging project! We appreciate your interest and support in making this project better.

Ways to Contribute

We welcome contribution in various forms, including but not limited to:

  • Reporting bugs or issues
  • Providing feedback on the existing codebase
  • Submitting fixes for identified issues
  • Proposing new features or enhancement
  • Improving documentation
  • Adding code snippets, algorithms, or techniques related to financial programming, deep learning, or machine learning

Code of Conduct

Please make sure to read and follow our Code of Conduct before contributing to the project.

Getting Started

Fork the repository

Create a personal copy of the Hedging-of-Financial-Derivatives repository on Github.

You can do this by clicking the Fork button on the Hedging-of-Financial-Derivatives repository page.

fork button

Clone the repository locally:

After forking the repository, clone it locally on your computer so that you can work on the code and make changes.

     $ git clone https://github.com/<YOUR-USERNAME>/Road_Lane_Detection_System..git

Create a new branch:

Before making any changes, create a new branch in your local repository.This is done to ensure that your changes are isolated from the main branch and can be easily reviewed and merged later.

    $ git checkout -b <branch-name>

Make changes:

Start making changes to the code, fixing bugs, adding new features, etc. Push changes to the fork:

Once the changes have been made, push them to your fork on Github.

$ git add .
$ git commit -m "Description of changes"
$ git push origin <branch-name>

Submitting a Pull Request

  • Make sure your changes are well-documented and include relevant tests.
  • If you've added new functionality, include appropriate documentation.
  • Follow the coding conventions used in the project.
  • Before submitting your pull request, make sure the following items have been checked:

    1. All tests pass and the build is successful.
    2. Your changes do not produce any new warnings or errors.
    3. Your changes have been thoroughly tested on different platforms and browsers.
    4. Your changes do not break backward compatibility.
    5. When you're ready, submit a pull request and include a descriptive title and a detailed description of your changes.
      1. Acknowledgement

        Contributors are an integral part of this project, and all contributions will be recognized and appreciated. Your efforts help us improve and grow this project.

        Thank you for your interest and contributions to our Hedging-of-Financial-Derivatives