added file task.ms

[OnkarBorude]

Summary by CodeRabbit

• Documentation
  • Added a new Day 7 task page to the documentation, introducing the assignment with a brief description.
  • Improves clarity and discoverability of daily tasks for users following the series. No impact on app features or behavior.

[coderabbitai]

Walkthrough

Adds a new Markdown file at 2023/day07/task.md with a single line of text and a trailing blank line. No code or interfaces changed.

Changes

Cohort / File(s)	Summary
Day 7 Task Doc 2023/day07/task.md	Added new Markdown file containing one line: "this is task of day 7" plus a trailing blank line.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I hop through commits, light as air,
A page appears—day seven’s fare.
One simple line, a gentle mark,
A breadcrumb left in timeline’s park.
With twitching whiskers, I approve—
Onward, onward—merge and move! 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "added file task.ms" indicates a file was added but misstates the filename/extension: the PR adds 2023/day07/task.md. Because the title correctly describes the primary action (adding a file) it is partially related to the changeset and meets the pass criteria, though the incorrect filename makes it less accurate.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

2023/day07/task.md (2)

1-2: Use a proper Markdown heading and fix grammar.

Propose turning this into a minimal, polished Markdown intro.

-this is task of day 7
+## Day 7: Task
+
+This is the task for Day 7.

---

1-2: PR title mentions “task.ms” but file added is “task.md”.

Please align the PR title or filename to avoid confusion.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4c3f0ea and 37b905c.

📒 Files selected for processing (1)

• 2023/day07/task.md (1 hunks)