-
-
Notifications
You must be signed in to change notification settings - Fork 706
README updates #1408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README updates #1408
Conversation
🦋 Changeset detectedLatest commit: f8859d2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
WalkthroughThis pull request modifies several Changes
Possibly related PRs
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (3)
packages/trigger-sdk/README.md (2)
1-14
: Great addition of logo and resource links!The centered logo with color scheme adaptation and the inclusion of various resource links significantly enhance the README's visual appeal and usability. This change makes it easier for users to access important information and community resources.
Consider adding alt text to the Twitter badge image for improved accessibility:
-[](https://twitter.com/triggerdotdev) +[](https://twitter.com/triggerdotdev)🧰 Tools
🪛 LanguageTool
[uncategorized] ~8-~8: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...f4f934bfae00/public"> ### Open source background jobs with no timeouts [Disc...(EN_COMPOUND_ADJECTIVE_INTERNAL)
20-27
: Improved "About" and "Getting started" sectionsThe addition of the "About" section and the expansion of the "Getting started" section provide valuable context and guidance for users. These changes will help new users understand the platform better and get started more quickly.
Consider adding a hyphen to "open source" in the "About" section for grammatical correctness:
-Trigger.dev is an open source platform and SDK which allows you to create long-running background jobs. +Trigger.dev is an open-source platform and SDK which allows you to create long-running background jobs.🧰 Tools
🪛 LanguageTool
[uncategorized] ~22-~22: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...r project. ## About Trigger.dev is an open source platform and SDK which allows you to cr...(EN_COMPOUND_ADJECTIVE_INTERNAL)
README.md (1)
20-31
: Improved presentation of key features.The changes in this section significantly enhance readability and provide a more comprehensive overview of Trigger.dev's capabilities. The bulleted list format makes it easier for users to scan and understand the key features.
Consider the following minor suggestion:
To maintain consistency with other headings, you might want to remove the colon after "Key features". This would address the Markdownlint warning without affecting the overall clarity.
-### Key features: +### Key features🧰 Tools
🪛 Markdownlint
20-20: Punctuation: ':'
Trailing punctuation in heading(MD026, no-trailing-punctuation)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (3)
- README.md (3 hunks)
- packages/cli-v3/README.md (1 hunks)
- packages/trigger-sdk/README.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md
[uncategorized] ~18-~18: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...## About Trigger.dev Trigger.dev is an open source platform and SDK which allows you to cr...(EN_COMPOUND_ADJECTIVE_INTERNAL)
packages/cli-v3/README.md
[grammar] ~17-~17: When ‘logged-in’ is used as a modifier, it is usually spelled with a hyphen.
Context: ...ds) | Display the current logged in user and project details. | ...(LOGGED_IN_HYPHEN)
packages/trigger-sdk/README.md
[uncategorized] ~8-~8: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...f4f934bfae00/public"> ### Open source background jobs with no timeouts [Disc...(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~22-~22: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...r project. ## About Trigger.dev is an open source platform and SDK which allows you to cr...(EN_COMPOUND_ADJECTIVE_INTERNAL)
🪛 Markdownlint
README.md
20-20: Punctuation: ':'
Trailing punctuation in heading(MD026, no-trailing-punctuation)
71-71: Expected: h2; Actual: h3
Heading levels should only increment by one level at a time(MD001, heading-increment)
71-71: Punctuation: ':'
Trailing punctuation in heading(MD026, no-trailing-punctuation)
🔇 Additional comments (8)
packages/trigger-sdk/README.md (3)
15-19
: Concise and informative introductionThe added description succinctly explains the purpose of the Trigger.dev SDK. It effectively communicates the main functionality to potential users.
28-34
: Helpful "SDK usage" and "Support" sectionsThe addition of the "SDK usage" and "Support" sections provides clear guidance for users who need more information or assistance. The link to the documentation and the invitation to join the Discord community are valuable resources for users at different stages of their journey with Trigger.dev.
1-34
: Overall excellent improvements to the READMEThe changes made to this README file significantly enhance its quality and usefulness. The additions of the logo, resource links, expanded sections, and clear guidance make the document more informative and user-friendly. These improvements will help new users quickly understand the Trigger.dev SDK and get started with the platform.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~8-~8: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...f4f934bfae00/public"> ### Open source background jobs with no timeouts [Disc...(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~22-~22: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...r project. ## About Trigger.dev is an open source platform and SDK which allows you to cr...(EN_COMPOUND_ADJECTIVE_INTERNAL)
README.md (5)
18-18
: Improved clarity in the project description.The rephrasing enhances the initial description by focusing on the core functionality of long-running background jobs. The removal of "with no timeouts" from this sentence is appropriate, as it's mentioned later in the key features.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~18-~18: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...## About Trigger.dev Trigger.dev is an open source platform and SDK which allows you to cr...(EN_COMPOUND_ADJECTIVE_INTERNAL)
55-55
: Enhanced deployment description.The updated description provides a clearer picture of Trigger.dev's deployment process. It effectively communicates the ease of use (no infrastructure management), automatic scaling, and the option for self-hosting. This gives potential users a better understanding of the platform's flexibility and capabilities.
69-71
: Improved "Getting started" instructions.The updated "Getting started" section provides clearer and more specific instructions for new users. By directing users to create an account and project in the web app and mentioning the onboarding process, it sets the right expectations and provides a straightforward path to begin using Trigger.dev. The promise of building and deploying the first task in minutes is an excellent motivator for potential users.
🧰 Tools
🪛 Markdownlint
71-71: Expected: h2; Actual: h3
Heading levels should only increment by one level at a time(MD001, heading-increment)
71-71: Punctuation: ':'
Trailing punctuation in heading(MD026, no-trailing-punctuation)
77-81
: Improved self-hosting information.The updates to the "Self-hosting" section enhance the information provided about this option. The link to the self-hosting guide gives users easy access to detailed instructions. Additionally, mentioning the dedicated self-hosting support channel in the Discord server is excellent, as it assures users that they can get help if needed.
The placement of this section after the "Useful links" is logical and helps maintain a good flow of information in the README.
Line range hint
1-100
: Overall excellent improvements to the README.The changes made to this README file significantly enhance its clarity, structure, and informativeness. The key improvements include:
- Better organization of information, especially in the "Key features" section.
- Clearer "Getting started" instructions.
- Addition of useful links for users at different stages.
- Improved information about self-hosting options.
These updates make the README more user-friendly and provide a better introduction to Trigger.dev for potential users. The minor suggestions provided in the review (heading levels and punctuation) will further improve the document's consistency and structure.
Great work on these updates!
🧰 Tools
🪛 LanguageTool
[uncategorized] ~18-~18: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...## About Trigger.dev Trigger.dev is an open source platform and SDK which allows you to cr...(EN_COMPOUND_ADJECTIVE_INTERNAL)
🪛 Markdownlint
20-20: Punctuation: ':'
Trailing punctuation in heading(MD026, no-trailing-punctuation)
- [Quick start](https://trigger.dev/docs/quick-start) - get up and running in minutes | ||
- [How it works](https://trigger.dev/docs/v3/how-it-works) - understand how Trigger.dev works under the hood | ||
- [Guides and examples](https://trigger.dev/docs/guides/introduction) - walk-through guides and code examples for popular frameworks and use cases | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great addition of "Useful links" section.
The new "Useful links" section is a valuable addition to the README. It provides easy access to essential resources for users at different stages of their Trigger.dev journey. The links to quick start, how it works, and guides and examples cover all the bases for new and experienced users alike.
However, there's a small structural issue to address:
The "Useful links" heading is currently an h3 (###), which is inconsistent with the document structure. To maintain consistency, change it to an h2 (##). Here's the suggested fix:
-### Useful links:
+## Useful links
This change will improve the document's structure and address the Markdownlint warning about heading increments.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
- [Quick start](https://trigger.dev/docs/quick-start) - get up and running in minutes | |
- [How it works](https://trigger.dev/docs/v3/how-it-works) - understand how Trigger.dev works under the hood | |
- [Guides and examples](https://trigger.dev/docs/guides/introduction) - walk-through guides and code examples for popular frameworks and use cases | |
## Useful links | |
- [Quick start](https://trigger.dev/docs/quick-start) - get up and running in minutes | |
- [How it works](https://trigger.dev/docs/v3/how-it-works) - understand how Trigger.dev works under the hood | |
- [Guides and examples](https://trigger.dev/docs/guides/introduction) - walk-through guides and code examples for popular frameworks and use cases |
commit: |
/trigger
during project initialization
#1412
Summary by CodeRabbit