Move vouch requirement to top of CONTRIBUTING.md (#3029)
Contributors need to be vouched before opening PRs, but this requirement was buried far down in the document. This change: - Adds mention of vouches in the intro paragraph - Moves the "Getting vouched" section to right after the intro This makes the requirement more visible to new contributors. Slack thread: https://triggerdotdev.slack.com/archives/C0A7Q6F62NS/p1770805895370749 https://claude.ai/code/session_01G6VVbgfUAeCpJfedELdqq1 <!-- devin-review-badge-begin --> --- <a href="https://app.devin.ai/review/triggerdotdev/trigger.dev/pull/3029" target="_blank"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://static.devin.ai/assets/gh-open-in-devin-review-dark.svg?v=1"> <img src="https://static.devin.ai/assets/gh-open-in-devin-review-light.svg?v=1" alt="Open with Devin"> </picture> </a> <!-- devin-review-badge-end --> Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
+14
-14
@@ -2,10 +2,23 @@
|
||||
|
||||
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 contributing best practices for Trigger.dev.
|
||||
Please take some time to read this guide to understand contributing best practices for Trigger.dev. Note that we use [vouch](https://github.com/mitchellh/vouch) to manage contributor trust, so you'll need to be vouched before opening a PR.
|
||||
|
||||
Thank you for helping us make Trigger.dev even better! 🤩
|
||||
|
||||
## Getting vouched (required before opening a PR)
|
||||
|
||||
We use [vouch](https://github.com/mitchellh/vouch) to manage contributor trust. **PRs from unvouched users are automatically closed.**
|
||||
|
||||
Before you open your first pull request, you need to be vouched by a maintainer. Here's how:
|
||||
|
||||
1. Open a [Vouch Request](https://github.com/triggerdotdev/trigger.dev/issues/new?template=vouch-request.yml) issue.
|
||||
2. Tell us what you'd like to work on and share any relevant background.
|
||||
3. A maintainer will review your request and vouch for you by commenting on the issue.
|
||||
4. Once vouched, your PRs will be accepted normally.
|
||||
|
||||
If you're unsure whether you're already vouched, go ahead and open a PR — the check will tell you.
|
||||
|
||||
## Developing
|
||||
|
||||
The development branch is `main`. This is the branch that all pull
|
||||
@@ -223,19 +236,6 @@ See the [Job Catalog](./references/job-catalog/README.md) file for more.
|
||||
4. Navigate to your trigger.dev instance ([http://localhost:3030](http://localhost:3030/)), to see the jobs.
|
||||
You can use the test feature to trigger them.
|
||||
|
||||
## Getting vouched (required before opening a PR)
|
||||
|
||||
We use [vouch](https://github.com/mitchellh/vouch) to manage contributor trust. **PRs from unvouched users are automatically closed.**
|
||||
|
||||
Before you open your first pull request, you need to be vouched by a maintainer. Here's how:
|
||||
|
||||
1. Open a [Vouch Request](https://github.com/triggerdotdev/trigger.dev/issues/new?template=vouch-request.yml) issue.
|
||||
2. Tell us what you'd like to work on and share any relevant background.
|
||||
3. A maintainer will review your request and vouch for you by commenting on the issue.
|
||||
4. Once vouched, your PRs will be accepted normally.
|
||||
|
||||
If you're unsure whether you're already vouched, go ahead and open a PR — the check will tell you.
|
||||
|
||||
## Making a pull request
|
||||
|
||||
**If you get errors, be sure to fix them before committing.**
|
||||
|
||||
Reference in New Issue
Block a user