Skip to content

Conversation

@leeunduck
Copy link
Owner

๐Ÿš€ Pull Request

๐Ÿ“ PR ์œ ํ˜•

  • ๊ธฐ๋Šฅ ์ถ”๊ฐ€ (Feature)
  • ๋ฒ„๊ทธ ์ˆ˜์ • (Bug Fix)
  • ์ฝ”๋“œ ๊ฐœ์„  (Refactoring)
  • ๋ฌธ์„œ ์ž‘์—… (Docs)
  • ํ™˜๊ฒฝ ์„ค์ • (Configuration)
  • ์ตœ์ข… ์ ๊ฒ€ (Release Check)

๐Ÿ” ๋ณ€๊ฒฝ ์‚ฌํ•ญ

Google Search Console ์†Œ์œ ๊ถŒ ํ™•์ธ ํ‚ค ์ถ”๊ฐ€


๐Ÿ“ธ ์Šคํฌ๋ฆฐ์ƒท


๐Ÿšง ๊ด€๋ จ ์ด์Šˆ


๐Ÿ› ๏ธ ์ตœ์ข… ๋ฐฐํฌ ์ ๊ฒ€ ๋ฆฌ์ŠคํŠธ

  • ์ฃผ์š” ๊ธฐ๋Šฅ ๋™์ž‘ ํ™•์ธ
  • ๋นŒ๋“œ/๋ฐฐํฌ ํ™˜๊ฒฝ ์ ๊ฒ€
  • ๋ฌธ์„œ/์„ค์ • ๊ฒ€ํ† 

โœ… ์ตœ์ข… ๋ฐฐํฌ ์ ๊ฒ€ ๊ฒฐ๊ณผ

@vercel
Copy link

vercel bot commented Oct 22, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
custom-daily-planner Ready Ready Preview Comment Oct 22, 2025 3:31pm

@leeunduck leeunduck merged commit 5354dc9 into main Oct 22, 2025
8 checks passed
@leeunduck leeunduck deleted the Chore/next-sitemap branch October 22, 2025 15:33
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

๐Ÿ’ก Codex Review

Here are some automated review suggestions for this pull request.

โ„น๏ธ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with ๐Ÿ‘.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 68 to +79
<html lang="ko">
<body>
{/*
<head>
<body>
{/*
Providers๋กœ ๊ฐ์‹ธ๋Š” ์ด์œ :
- React Query์˜ QueryClientProvider๋ฅผ ์ „์—ญ ์ ์šฉ
- ๋ชจ๋“  ํ•˜์œ„ ์ปดํฌ๋„ŒํŠธ๊ฐ€ ๋™์ผํ•œ client & cache ๊ณต์œ 
- useQuery, useMutation ํ›…์ด ์–ด๋””์„œ๋“  ์ •์ƒ ๋™์ž‘
*/}
<Providers>{children}</Providers>
</body>
<Providers>{children}</Providers>
</body>
</head>

Choose a reason for hiding this comment

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

P1 Badge Avoid nesting <body> inside <head> in root layout

The commit wraps the entire application <body> inside a <head> element. In Next.js app layouts the <html> element must contain sibling <head> and <body> sections; placing <body> inside <head> violates HTML semantics and will trigger DOM nesting warnings and hydration mismatches, meaning the metadata system and Providers component may not mount correctly. Remove the extra <head> wrapper so <body> remains a direct child of <html>.

Useful? React with ๐Ÿ‘ย / ๐Ÿ‘Ž.

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.

2 participants