Skip to content

added onboarding documentation#31

Open
kozachokv wants to merge 1 commit intokoldovsky:mainfrom
kozachokv:patch-1
Open

added onboarding documentation#31
kozachokv wants to merge 1 commit intokoldovsky:mainfrom
kozachokv:patch-1

Conversation

@kozachokv
Copy link
Copy Markdown

@kozachokv kozachokv commented Mar 27, 2026

Summary by CodeRabbit

  • Documentation
    • Comprehensive engineering onboarding guide added, covering project architecture, technical stack, development workflow, contribution guidelines, coding standards, CI/CD overview, and common pitfalls to help new contributors get started.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 27, 2026

📝 Walkthrough

Walkthrough

README.md content replaced from minimal "Task 01" placeholder with comprehensive "Excalidraw Engineering Onboarding Guide," including project overview, monorepo structure, technical stack, development workflows, contribution guidelines, CI/CD details, and best practices.

Changes

Cohort / File(s) Summary
Documentation
README.md
Replaced placeholder task content with extensive onboarding guide featuring project overview, monorepo architecture, directory structure, technical stack, development commands, contribution workflow, CI/CD overview, coding standards, common pitfalls, first-week plan, and reference material.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A guide so grand, now polished bright,
With diagrams and workflows set just right,
Onboarding paths both clear and wide,
Fellow contributors—hop on inside! 🌿

🚥 Pre-merge checks | ✅ 3
✅ 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 onboarding documentation' directly and clearly summarizes the main change: comprehensive onboarding documentation added to README.md.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

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

Copy link
Copy Markdown

@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

🧹 Nitpick comments (1)
README.md (1)

141-145: Avoid making snapshot updates a default pre-PR step.

Putting yarn test:update first in the checklist can encourage unnecessary snapshot churn. Recommend yarn test by default and reserve test:update for intentional snapshot changes only.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 141 - 145, The checklist currently lists "yarn
test:update" as the first pre-PR step which encourages accidental snapshot
churn; change the order and wording so the default step is "yarn test" (or
similar) and make "yarn test:update" explicit as an optional step only when
snapshots are intentionally changed; update the README checklist entries
referencing "yarn test", "yarn test:update", "yarn test:typecheck", "yarn
test:code", and "yarn test:other" to reflect this new ordering and note that
snapshot updates must be intentional.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Around line 175-182: The README lists several CI/workflow files that don't
exist (lint.yml, test.yml, test-coverage-pr.yml, size-limit.yml,
semantic-pr-title.yml); update the README or the repo so they match: either
remove or comment out the bullet entries for those workflows in README.md, or
add the missing workflow/config files with the referenced names (lint.yml,
test.yml, test-coverage-pr.yml, size-limit.yml, semantic-pr-title.yml) and
ensure their paths and names match the README; keep the README’s “Important
workflows include” section consistent with actual files and include brief notes
on where each workflow lives if you add them.

---

Nitpick comments:
In `@README.md`:
- Around line 141-145: The checklist currently lists "yarn test:update" as the
first pre-PR step which encourages accidental snapshot churn; change the order
and wording so the default step is "yarn test" (or similar) and make "yarn
test:update" explicit as an optional step only when snapshots are intentionally
changed; update the README checklist entries referencing "yarn test", "yarn
test:update", "yarn test:typecheck", "yarn test:code", and "yarn test:other" to
reflect this new ordering and note that snapshot updates must be intentional.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e32c5d2a-2176-4198-a225-e81c75b5cb56

📥 Commits

Reviewing files that changed from the base of the PR and between be47f1d and 61aab60.

📒 Files selected for processing (1)
  • README.md

Comment on lines +175 to +182
Important workflows include:
- `lint.yml`: lint + type checks
- `test.yml`: test execution
- `test-coverage-pr.yml`: coverage reporting
- `size-limit.yml`: package size control
- `semantic-pr-title.yml`: PR title convention check
- Release/deployment workflows for package and docker pipelines

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify that README-referenced workflow/config/doc files currently exist.

set -euo pipefail

echo "== Checking workflow files =="
for f in \
  ".github/workflows/lint.yml" \
  ".github/workflows/test.yml" \
  ".github/workflows/test-coverage-pr.yml" \
  ".github/workflows/size-limit.yml" \
  ".github/workflows/semantic-pr-title.yml"
do
  if [ -f "$f" ]; then
    echo "FOUND  $f"
  else
    echo "MISSING $f"
  fi
done

echo
echo "== Checking referenced docs/config files =="
for f in \
  "README.md" \
  "CONTRIBUTING.md" \
  "dev-docs/docs/introduction/development.mdx" \
  "dev-docs/docs/introduction/contributing.mdx" \
  "packages/excalidraw/README.md" \
  "package.json" \
  "tsconfig.json" \
  ".eslintrc.json" \
  ".editorconfig" \
  "vitest.config.mts"
do
  if [ -f "$f" ]; then
    echo "FOUND  $f"
  else
    echo "MISSING $f"
  fi
done

Repository: koldovsky/is-01-docs

Length of output: 640


Update README to remove references to non-existent workflows and config files, or add the missing files.

Verification found that all workflow files referenced in this section are missing: lint.yml, test.yml, test-coverage-pr.yml, size-limit.yml, and semantic-pr-title.yml. Most referenced config/doc files also don't exist (only README.md was found). This creates a significant onboarding problem—new contributors following the README will search for these files and hit dead ends.

Either remove the references to workflows/configs that don't exist, or ensure the files are present and paths are correct.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 175 - 182, The README lists several CI/workflow files
that don't exist (lint.yml, test.yml, test-coverage-pr.yml, size-limit.yml,
semantic-pr-title.yml); update the README or the repo so they match: either
remove or comment out the bullet entries for those workflows in README.md, or
add the missing workflow/config files with the referenced names (lint.yml,
test.yml, test-coverage-pr.yml, size-limit.yml, semantic-pr-title.yml) and
ensure their paths and names match the README; keep the README’s “Important
workflows include” section consistent with actual files and include brief notes
on where each workflow lives if you add them.

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.

1 participant