Fixes a docs link and tweaks some wording for the triggering task blank state

[samejr]

On the Runs list page when you have a task but haven't done a run yet:

• Fixes a docs link to point to the "triggering" docs page
• Improves the wording on the blank state
• Updates the button styles to be consistent

Summary by CodeRabbit

• Documentation

  • Revised on-page instructions to clearly guide users when performing test runs and triggering tasks.
  • Updated text for improved clarity and consistency in messaging.

• Style

  • Refined button appearances with updated styles and icon colors.
  • Adjusted navigation links to direct users to the appropriate resources.

[coderabbitai]

Walkthrough

The pull request updates the text and styling details in the RunTaskInstructions function within the route file. The test run instructions now read “Perform a test run with a payload directly from the dashboard,” and the corresponding LinkButton’s styling is adjusted by modifying its variant and adding a new icon class. Similarly, the real run instructions have been updated for consistent capitalization, and its associated LinkButton now uses a dynamic URL and updated variant styling.

Changes

File Path	Change Summary
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.runs._index/route.tsx	- Updated test run instruction text - Changed test run button variant from primary/medium to secondary/medium and added leadingIconClassName: "text-lime-500" - Revised real run instructions text for consistent capitalization - Updated trigger button URL from a static URL to docsPath("/triggering") and changed its variant to docs/medium with updated button text

Suggested reviewers

• matt-aitken
• ericallam

Poem

I hopped through the code with delight,
Tweaking texts and buttons so bright.
The style now shows a fresh, green gleam,
Making the dashboard a smoother dream.
With a skip and a bound, my code sings anew—
A rabbit’s cheer for changes true!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 394f1de and 4043802.

📒 Files selected for processing (1)

• apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.runs._index/route.tsx (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: units / 🧪 Unit Tests
• GitHub Check: typecheck / typecheck
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (4)

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.runs._index/route.tsx (4)

465-465: Improved instruction clarity

The simplified wording makes the instruction more direct and actionable for users who encounter the blank state.

---

467-472: Consistent button styling and improved visual hierarchy

Good adjustment to the button variant and the addition of the lime-colored icon. The change from "primary" to "secondary" variant helps establish a proper visual hierarchy between the two action buttons on this page, while the colored icon improves scanability.

---

486-486: Corrected capitalization for consistency

Fixed the inconsistent capitalization of "trigger" and "task", which helps maintain uniform terminology throughout the application.

---

488-495: Fixed documentation link and improved button consistency

The changes correctly implement:

1. Using docsPath("/triggering") to link to the appropriate documentation section
2. Using the "docs/medium" variant which is more semantically appropriate for documentation links
3. Updating the button text from "How to run a task" to "How to trigger a task" to use consistent terminology

These changes ensure users are directed to the right documentation and maintain consistent UI patterns.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.