Skip to content

fix: vercel.json#307

Merged
seong-hui merged 1 commit intodevelopfrom
fix/#306
Aug 2, 2025
Merged

fix: vercel.json#307
seong-hui merged 1 commit intodevelopfrom
fix/#306

Conversation

@seong-hui
Copy link
Member

@seong-hui seong-hui commented Aug 2, 2025

🛰️ 관련 이슈

해결한 이슈 번호를 작성해주세요
close #306

🧑‍💻 작업 내용

작업한 내용을 간략히 작성해주세요

Error: Project names can be up to 100 characters long and must be lowercase. They can include letters, digits, and the following characters: '.', '_', '-'. However, they cannot contain the sequence '---'. (400)
배포하는데 해당 에러가 발생해서 vercel.json에 name을 추가해보았슴다

🗯️ PR 포인트

리뷰어가 특별히 봐주었으면 하는 부분이 있다면 작성해주세요

🚀 알게된 점

기록하며 개발하기!

📖 참고 자료 (선택)

참고했던 문서들 공유하기!

📸 스크린샷 (선택)

Summary by CodeRabbit

  • Chores
    • Vercel 배포 설정에 프로젝트 이름이 추가되었습니다.

@coderabbitai
Copy link

coderabbitai bot commented Aug 2, 2025

Walkthrough

vercel.json 파일에 "name": "web-jeolloga" 속성이 추가되었습니다. 기존 "framework": "nextjs" 설정은 그대로 유지되었으며, 이번 변경으로 Vercel 프로젝트의 이름이 명시적으로 지정되었습니다.

Changes

Cohort / File(s) Change Summary
Vercel 설정 파일
vercel.json
"name" 속성 추가 및 프로젝트 이름 명시

Sequence Diagram(s)

(해당 변경은 설정 파일의 속성 추가로, 시퀀스 다이어그램이 필요하지 않습니다.)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Assessment against linked issues

Objective Addressed Explanation
넥제 배포 에러 해결을 위한 프로젝트 이름 명시 (#306)

Assessment against linked issues: Out-of-scope changes

(연관 이슈 목표 외의 변경 사항이 없습니다.)

Poem

🐰
설정에 이름을 달아주었죠,
"web-jeolloga"라 부르기로 했어요.
배포 에러는 이제 안녕,
토끼는 기쁘게 뛰놀아요!

🎉✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 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 9bb06c7 and 5192b7b.

📒 Files selected for processing (1)
  • vercel.json (1 hunks)
🔇 Additional comments (1)
vercel.json (1)

2-3: 프로젝트 이름 필드 추가 👍

"name": "web-jeolloga" 값이 소문자이며 허용된 문자만 포함하고 길이도 제한 내에 있어 Vercel 네이밍 규칙을 충족합니다. 배포 오류 해결에 적절한 수정으로 보입니다.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/#306

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @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.

@github-actions
Copy link

github-actions bot commented Aug 2, 2025

🪷 Storybook 확인 🪷
🔗 https://677fa9af1269762b7858c29f-faptnyifux.chromatic.com/

Copy link
Collaborator

@maylh maylh left a comment

Choose a reason for hiding this comment

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

두근두근

Copy link
Collaborator

@bykbyk0401 bykbyk0401 left a comment

Choose a reason for hiding this comment

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

어푸어푸

@seong-hui seong-hui merged commit e050e2e into develop Aug 2, 2025
7 checks passed
@seong-hui seong-hui deleted the fix/#306 branch August 2, 2025 14:03
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.

[FIX] next deploy 에러

3 participants