Tweak stage 2 terminal instructions

[andy1li]

Checklist:

• I've thoroughly self-reviewed my changes
• I've added tests for my changes, unless they affect admin-only areas (or are otherwise not worth testing)
• I've verified any visual changes using Percy (add a commit with [percy] in the message to trigger)

Summary by CodeRabbit

• Documentation
  • Updated instructional text for the "shell" course stage tutorial card
  • Clarified error handling instructions for invalid command implementation

[coderabbitai]

Walkthrough

The pull request updates the instructional text within the CoursePage::InstructionsCard component for the "shell" course. The modification focuses on clarifying the task description for the second stage tutorial, specifically changing the instructions to emphasize error handling for invalid commands. The change provides a more precise directive about treating all commands as invalid during this stage, while maintaining the existing component structure and rendering logic.

Changes

File	Change Summary
app/components/course-page/course-stage-step/second-stage-tutorial-card.hbs	Updated instructional text for "shell" course, specifying error handling for invalid commands

Possibly related PRs

• End stage 2 experiment: Short Instructions vs Link to Code Examples #2517: Modifies CoursePage::InstructionsCard component's conditional rendering logic
• Launch Terminal Instructions experiment for Shell stage 1 and 2 #2521: Enhances rendering logic for terminal instructions in the "shell" course

Suggested reviewers

• rohitpaulk

Poem

🐰 A Shell's Tale of Error's Might

In lines of code, a rabbit's delight
Invalid commands, now crystal clear
With instructions sharp and bright
Learning grows without a fear!

🖥️ Code on, brave coder, take flight!

---

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

• 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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

app/components/course-page/course-stage-step/second-stage-tutorial-card.hbs (1)

Line range hint 47-51: Consider removing or updating the hardcoded completion rate

The hardcoded 98% completion rate might be misleading if it's not regularly updated. Consider either:

1. Removing it until the TODO is implemented
2. Fetching real-time statistics from the backend
3. Adding a note that this is an approximate figure

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between dc179a2 and 493b2da.

📒 Files selected for processing (1)

• app/components/course-page/course-stage-step/second-stage-tutorial-card.hbs (1 hunks)

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

• GitHub Check: test

🔇 Additional comments (1)

app/components/course-page/course-stage-step/second-stage-tutorial-card.hbs (1)

7-7: Great improvement in instruction clarity!

The updated text makes it explicitly clear that students should treat all commands as invalid at this stage. This aligns well with the visual example and tooltips below, creating a more cohesive learning experience.

[github-actions]

Test Results

  1 files  ±0    1 suites  ±0   5m 56s ⏱️ - 1m 24s
595 tests ±0  554 ✅ ±0  41 💤 ±0  0 ❌ ±0 
610 runs  ±0  569 ✅ ±0  41 💤 ±0  0 ❌ ±0 

Results for commit 493b2da. ± Comparison against base commit dc179a2.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files

📢 Thoughts on this report? Let us know!

[andy1li]

Thanks 1Dedios for the suggestion!