chore: rename repo

[noahluftyang]

Changes

• 레포 이름 변경해요~

Visuals

Checklist

• Have you written the functional specifications?
• Have you written the test code?

Additional Discussion Points

Summary by CodeRabbit

• Chores

  • 프로젝트 저장소 관련 링크와 참조를 최신 정보로 업데이트하였습니다.

• Documentation

  • 문서, 가이드라인, 뱃지 및 내비게이션 링크를 새 저장소 명칭에 맞게 수정하여 사용자에게 제공되는 정보의 일관성과 신뢰성을 높였습니다.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f83c864

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

이 풀 리퀘스트는 저장소 URL 참조를 갱신하는 변경 사항을 포함합니다. 기존의 "3-2_side" URL이 "side"로 업데이트되었으며, 문서, 패키지 구성 파일 및 사이트 설정 파일(www/docusaurus.config.ts) 등 여러 파일에서 해당 URL과 관련된 명령어, 배지 링크, 및 프로젝트 이름이 일관되게 수정되었습니다.

Changes

File(s)	Change Summary
.github/CONTRIBUTING.md, docs/introduction.mdx	저장소 URL 업데이트 ("3-2_side" → "side")
README.md	MIT 라이선스, 코드 커버리지, 기여자 링크 및 배지 이미지 URL 업데이트
.templates/component/package.json	repository URL 업데이트 ("3-2_side" → "side")
packages/*/package.json	repository URL 업데이트 ("3-2_side" → "side"); packages/grid는 파일 배열 형식 수정 포함
www/docusaurus.config.ts	프로젝트 이름 및 관련 URL(editUrl, GitHub 링크) 업데이트 ("3-2_side" → "side")

Poem

깡충깡충 토끼가 외치네,
옛 이름은 뒤로하고 새 길을 걷네,
URL이 바뀌어도 마음은 한결같아,
코드의 숲 속을 함께 달려가네,
저장소의 변화에 즐거운 발자취 남기네 🐰

---

📜 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 7abd2b5 and f83c864.

📒 Files selected for processing (23)

• .github/CONTRIBUTING.md (1 hunks)
• .templates/component/package.json (1 hunks)
• README.md (2 hunks)
• docs/introduction.mdx (1 hunks)
• packages/Input/package.json (1 hunks)
• packages/avatar/package.json (1 hunks)
• packages/badge/package.json (1 hunks)
• packages/button/package.json (1 hunks)
• packages/card/package.json (1 hunks)
• packages/checkbox/package.json (1 hunks)
• packages/divider/package.json (1 hunks)
• packages/flex/package.json (1 hunks)
• packages/grid/package.json (1 hunks)
• packages/icon/package.json (1 hunks)
• packages/radio-group/package.json (1 hunks)
• packages/reset/package.json (1 hunks)
• packages/side/package.json (1 hunks)
• packages/skeleton/package.json (1 hunks)
• packages/switch/package.json (1 hunks)
• packages/tokens/package.json (1 hunks)
• packages/tooltip/package.json (1 hunks)
• packages/typography/package.json (1 hunks)
• www/docusaurus.config.ts (3 hunks)

✅ Files skipped from review due to trivial changes (22)

• packages/reset/package.json
• packages/flex/package.json
• packages/Input/package.json
• packages/tooltip/package.json
• packages/divider/package.json
• packages/icon/package.json
• packages/tokens/package.json
• packages/switch/package.json
• packages/card/package.json
• docs/introduction.mdx
• .github/CONTRIBUTING.md
• packages/badge/package.json
• packages/button/package.json
• packages/skeleton/package.json
• packages/grid/package.json
• packages/checkbox/package.json
• packages/avatar/package.json
• packages/side/package.json
• packages/radio-group/package.json
• packages/typography/package.json
• .templates/component/package.json
• README.md

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

• GitHub Check: CI

🔇 Additional comments (3)

www/docusaurus.config.ts (3)

12-12: 프로젝트 이름 변경이 적절합니다!

저장소 이름 변경에 맞춰 프로젝트 이름이 정확하게 업데이트되었습니다.

---

57-57: GitHub 링크가 올바르게 업데이트되었습니다.

네비게이션 바의 GitHub 링크가 새로운 저장소 이름으로 정확하게 변경되었습니다.

저장소 URL이 유효한지 확인해보세요:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Verify the GitHub repository URL is accessible
curl -I "https://github.com/sipe-team/side"

Length of output: 4884

---

네비게이션 바의 GitHub 링크 검증 완료

• GitHub URL이 "https://github.com/sipe-team/side"로 업데이트 되었으며, curl 검증 결과 HTTP 200 응답을 받아 올바르게 접근 가능함이 확인되었습니다.

---

25-25: 문서 편집 URL이 올바르게 업데이트되었습니다.

새로운 저장소 이름이 문서 편집 URL에 정확하게 반영되었습니다.

URL이 실제로 접근 가능한지 확인해보세요:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Verify the documentation edit URL is accessible
curl -I "https://github.com/sipe-team/side/tree/main/www/"

Length of output: 4917

---

문서 편집 URL 업데이트 확인

문서 편집 URL이 새 저장소 이름을 올바르게 반영하며, 실제로 접근 가능한 것으로 확인되었습니다.

• URL: https://github.com/sipe-team/side/tree/main/www/
• 확인 결과: HTTP/2 200 응답 (정상 접근)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.

[froggy1014]

Lets go. 🚀

[hy57in]

우와.