Skip to content

Latest commit

 

History

History
30 lines (18 loc) · 1.31 KB

CONTRIBUTING_GUIDELINES.md

File metadata and controls

30 lines (18 loc) · 1.31 KB

For updating cost calculations - Please follow the README.md in the cost/ directory.

Contributing to Helicone

There are many ways to contribute to Helicone. Here are some guidelines to help you get started.

We Use Github Flow, So All Code Changes Happen Through Pull Requests

Pull requests are the best way to propose changes to the codebase:

  1. Fork the repo and create your branch from main.
  2. If you've added code that should be tested, add tests.
  3. Ensure the test suite passes.
  4. Make sure your code lints.
  5. Issue that pull request!

Any contributions you make will be under the Apache License

In short, when you submit code changes, your submissions are understood to be under the same Apache License that covers the project.

Report bugs using Github's issues

Spotted a bug? Has deployment gone wrong? Do you have user feedback? Raise an issue or reach out to us on Discord

... or pick up and fix an issue if you want to do a Pull Request.

Feature requests

Raise an issue for these and tag it as an Enhancement. We love every idea. Please give us as much context on the why as possible.