Thank you for taking the time to contribute to Trigger.dev. Your involvement is not just welcomed, but we encourage it! 🚀
Please take some time to read this guide to understand best practices for reporting issues, suggesting features, submitting code, creating PRs, and more.
Thank you for helping us make Trigger.dev even better! 🤩
Please help us maintain a positive and respectful environment by adhering to our community's Code of Conduct.
All submissions require review via a pull request.
If you spot a issue, search existing PRs or issues for any open or closed submission that relates to your submission. If a related issue doesn't exist, you can open a new issue.
Scan through our existing issues to find one that interests you. You can narrow down the search using labels as filters. If you find an issue to work on, you are welcome to open a PR with a fix.
We welcome all feature requests, both for new functionality to something that already exists or a brand new idea.
File your feature request through GitHub Issues here.
When making pull requests to the repository, make sure to follow these guidelines for both bug fixes and new features.
Before creating pull requests for new features, first file a GitHub Issue describing the reasoning and motivation for the feature. This gives maintainers and the community the opportunity to provide feedback on your idea before implementing it.
By contributing to Trigger.dev, you agree that your contributions will be licensed under its license specified in the repository you are contributing to.