Skip to content

Latest commit

 

History

History
49 lines (39 loc) · 2.45 KB

CONTRIBUTING.md

File metadata and controls

49 lines (39 loc) · 2.45 KB

Contributing

We're always looking for your help to fix bugs and improve the product. Create a pull request and we'll be happy to take a look. Start by reading the Engineering Design. You can find the doxygen generated documentation here.

Checkin procedure

  1. Fork the repo
  2. git clone your fork
  3. Create feature branch
  4. Make and checkin your changes along with unit tests
  5. git commit your changes
  6. git push origin HEAD
  7. To request merge into master send a pull request from the web ui https://github.com/Microsoft/onnxruntime.
  8. Add 'Microsoft/onnxruntime' as a reviewer.

New code must be accompanied by unit tests.

Note: After creating a pull request, you might not see a build getting triggered right away. One of the onnxruntime team members will trigger the build for you.

Build

Build

Coding guidelines

Please see Coding Conventions and Standards

Licensing guidelines

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.

Code of conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Reporting Security Issues

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at [email protected]. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.