Skip to content

Latest commit

Β 

History

History
71 lines (44 loc) Β· 4.3 KB

CONTRIBUTING.md

File metadata and controls

71 lines (44 loc) Β· 4.3 KB

Contributing to Novu

Thank you for showing an interest in contributing to Novu! All kinds of contributions are valuable to us. In this guide, we will cover how you can quickly onboard and make your first contribution.

Submitting an issue

Before submitting a new issue, please search the issues and discussion tabs. Maybe an issue or discussion already exists and might inform you of workarounds. Otherwise, you can give new information.

While we want to fix all the issues, before fixing a bug we need to be able to reproduce and confirm it. Please provide us with a minimal reproduction scenario using a repository or Gist. Having a live, reproducible scenario gives us the information without asking questions back & forth with additional questions like:

  • 3rd-party libraries being used and their versions (mainly providers, but not exclusively)
  • a use-case that fails

Without said minimal reproduction, we won't be able to investigate all issues, and the issue might not be resolved.

You can open a new issue with this issue form.

Projects setup and Architecture

Requirements

Setup the project

The project is a monorepo, meaning that it is a collection of multiple packages managed in the same repository.

To learn more about the project structure visit https://docs.novu.co/community/monorepo-structure.

After cloning your fork, you will need to run the npm run setup:project command to install and build all dependencies.

To learn a detailed guide on running the project locally, visit https://docs.novu.co/community/run-locally.

Missing a Feature?

If a feature is missing, you can directly request a new one here. You also can do the same by choosing "πŸš€ Feature" when raising a New Issue on our GitHub Repository. If you would like to implement it, an issue with your proposal must be submitted first, to be sure that we can use it. Please consider the guidelines given below.

Coding guidelines

To ensure consistency throughout the source code, please keep these rules in mind as you are working:

  • All features or bug fixes must be tested by one or more specs (unit-tests).
  • We use Eslint default rule guide, with minor changes. An automated formatter is available using prettier.

Need help? Questions and suggestions

Questions, suggestions, and thoughts are most welcome. Feel free to open a GitHub Discussion. We can also be reached in our Discord Server.

Ways to contribute

  • Try the Novu API and platform and give feedback
  • Add new providers
  • Help with open issues or create your own
  • Share your thoughts and suggestions with us
  • Help create tutorials and blog posts
  • Request a feature by submitting a proposal
  • Report a bug
  • Improve documentation - fix incomplete or missing docs, bad wording, examples or explanations.

Missing a provider?

If you are in need of a provider we do not yet have, you can request a new one by submitting an issue. Or you can build a new one by following our create a provider guide.