Skip to content

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

Merged
merged 4 commits into from
Oct 14, 2024
Merged

README updates #1408

merged 4 commits into from
Oct 14, 2024

Conversation

D-K-P
Copy link
Member

@D-K-P D-K-P commented Oct 14, 2024

Summary by CodeRabbit

  • Documentation
    • Enhanced clarity and structure in the README files for Trigger.dev, CLI, and SDK.
    • Improved organization of features and setup instructions for easier navigation.
    • Added new sections for useful links and support resources, including Discord links.
    • Reformatted command functionalities in the CLI README into a concise table format.
    • Introduced a centered logo section in the SDK README with links to community and documentation.

Copy link

changeset-bot bot commented Oct 14, 2024

🦋 Changeset detected

Latest commit: f8859d2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 9 packages
Name Type
trigger.dev Patch
@trigger.dev/sdk Patch
@trigger.dev/build Patch
@trigger.dev/core Patch
@trigger.dev/database Patch
@trigger.dev/otlp-importer Patch
@internal/redis-worker Patch
@internal/zod-worker Patch
@internal/testcontainers Patch

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

Copy link
Contributor

coderabbitai bot commented Oct 14, 2024

Walkthrough

This pull request modifies several README.md files across the Trigger.dev project, including the main project, CLI, and SDK documentation. The changes focus on enhancing clarity and structure, including rephrasing, reorganizing content into lists, and expanding sections for better user guidance. New sections have been added, such as "Useful links" and "Support," while existing sections have been streamlined. Overall, these modifications aim to improve the readability and navigability of the documentation.

Changes

File Path Change Summary
README.md - Adjusted section titles for consistency.
- Reformatted features into a bulleted list.
- Expanded "Getting started" section with clearer instructions.
- Added "Useful links" section and reorganized self-hosting information.
packages/cli-v3/README.md - Replaced "Usage" section with "Commands" table.
- Consolidated command functionalities with brief descriptions and links.
- Added a "Support" section.
packages/trigger-sdk/README.md - Introduced a centered logo section with community and documentation links.
- Updated description for clarity.
- Expanded "Getting started" section for user guidance.

Possibly related PRs

  • v3: self-hosting support for latest packages #1319: This PR focuses on enhancing self-hosting capabilities, which aligns with the changes made in the main PR regarding the self-hosting documentation updates.
  • Update self-hosting docs #1354: This PR updates self-hosting documentation, providing clearer instructions and troubleshooting guidance, which is related to the main PR's focus on improving documentation clarity.
  • Moving the docs examples section into guides #1356: This PR consolidates examples into guides, which may relate to the overall documentation restructuring seen in the main PR.
  • Webhook guides #1396: This PR introduces webhook guides, which could be relevant as it enhances the documentation structure, similar to the main PR's focus on improving the README.md for better clarity and organization.

Poem

In the garden of docs, we tidy and play,
With features and links, we brighten the way.
A hop here, a skip, to knowledge we bound,
In clarity's embrace, new friends will be found.
So gather 'round, bunnies, let’s share what we’ve made,
For in every fine change, a new path is laid! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 49365ec and f8859d2.

📒 Files selected for processing (1)
  • .changeset/cool-keys-sit.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • .changeset/cool-keys-sit.md

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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:

-[![Twitter](https://img.shields.io/twitter/url/https/twitter.com/triggerdotdev.svg?style=social&label=Follow%20%40trigger.dev)](https://twitter.com/triggerdotdev)
+[![Twitter Follow](https://img.shields.io/twitter/url/https/twitter.com/triggerdotdev.svg?style=social&label=Follow%20%40trigger.dev)](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" sections

The 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

📥 Commits

Files that changed from the base of the PR and between 1c80a74 and 49365ec.

📒 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 introduction

The 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" sections

The 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 README

The 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:

  1. Better organization of information, especially in the "Key features" section.
  2. Clearer "Getting started" instructions.
  3. Addition of useful links for users at different stages.
  4. 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)

Comment on lines +73 to +76
- [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

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

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.

Suggested change
- [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

Copy link

pkg-pr-new bot commented Oct 14, 2024

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/build@1408
pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/core@1408
pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev@1408
pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/sdk@1408

commit: f8859d2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants