[hotfix] 가이드 이미지 403 에러 수정

[ff1451]

✨ 요약

가이드 이미지의 경로에 한글이 들어가있어 에러가 발생하는 문제를 수정합니다.

Summary by CodeRabbit

릴리스 노트

• Documentation

  • Pull Request 작성 가이드 템플릿 추가

• 일반 개선

  • 가이드 이미지 리소스 표준화

[coderabbitai]

Walkthrough

GitHub Pull Request 템플릿이 새롭게 추가되었습니다. 템플릿은 요약, 해결된 이슈 섹션을 포함하며 기본 구조를 제공합니다. 동시에 가이드 데이터에서 이미지 파일명이 한글 기반 네이밍(가이드1.webp, 순공시간_개인별.webp)에서 숫자 기반 네이밍(1.webp부터 5.webp)으로 변경되어, 생성되는 가이드 아이템의 이미지 URL이 업데이트됩니다.

Possibly related PRs

• [refactor] 가이드 페이지 이미지 변경 및 구조 개선 #260: src/pages/Guide/guideData.ts의 가이드 이미지 파일명 및 URL 생성 로직이 동일하게 수정되어 있습니다.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목이 PR의 주요 변경사항을 명확하게 설명합니다. 가이드 이미지 경로의 한글 제거로 인한 403 에러 수정이 핵심 변경사항이며, 제목이 이를 정확히 반영하고 있습니다.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch hotfix/guide-image-403-fix

---

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: 1

🧹 Nitpick comments (1)

.github/ISSUE_TEMPLATE/PULL_REQUEST_TEMPLATE.md (1)

7-13: 템플릿 가독성을 위해 <br><br>는 제거를 권장합니다.

Markdown 템플릿에서는 빈 줄만으로도 충분히 구분돼서, HTML 태그를 빼면 유지보수가 더 깔끔해집니다.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/ISSUE_TEMPLATE/PULL_REQUEST_TEMPLATE.md around lines 7 - 13, Remove
the explicit HTML line breaks `<br><br>` from the template around the "## 😎 해결한
이슈" section and replace them with plain Markdown blank lines (i.e., ensure a
single empty line above and below the header and list content) so the template
uses markdown spacing instead of HTML; search for the `<br><br>` tokens in the
PULL_REQUEST_TEMPLATE.md and delete them, keeping the header "## 😎 해결한 이슈" and
its "- close" list item intact with proper blank-line separation.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/ISSUE_TEMPLATE/PULL_REQUEST_TEMPLATE.md:
- Line 11: Replace the vague placeholder "- close" with a clear issue-close
template such as "- close `#이슈번호`" and add a short inline hint so authors know to
replace "#이슈번호" with the actual issue number (e.g., "- close #<issue-number>").
Update the template line that currently contains "- close" to use this new
default and ensure surrounding PR template sections mention the expected format
(요약 / 😎 해결한 이슈) so contributors follow the `close `#이슈번호`` convention.

---

Nitpick comments:
In @.github/ISSUE_TEMPLATE/PULL_REQUEST_TEMPLATE.md:
- Around line 7-13: Remove the explicit HTML line breaks `<br><br>` from the
template around the "## 😎 해결한 이슈" section and replace them with plain Markdown
blank lines (i.e., ensure a single empty line above and below the header and
list content) so the template uses markdown spacing instead of HTML; search for
the `<br><br>` tokens in the PULL_REQUEST_TEMPLATE.md and delete them, keeping
the header "## 😎 해결한 이슈" and its "- close" list item intact with proper
blank-line separation.

🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2d8f204c-e448-4a2e-93e8-75d15be89cbf

📥 Commits

Reviewing files that changed from the base of the PR and between 45dc5eb and a454380.

📒 Files selected for processing (2)

• .github/ISSUE_TEMPLATE/PULL_REQUEST_TEMPLATE.md
• src/pages/Guide/guideData.ts

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

이슈 자동 닫힘 포맷 placeholder를 명확히 해주세요.

- close만 있으면 작성자가 형식을 놓치기 쉬워요. - close #이슈번호``로 기본값을 넣어두는 게 좋습니다.

제안 수정안

-- close
+- close `#이슈번호`

Based on learnings: Use PR template sections ✨ 요약 / 😎 해결한 이슈 and issue format close #이슈번호``.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- close
	- close `#이슈번호`

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/ISSUE_TEMPLATE/PULL_REQUEST_TEMPLATE.md at line 11, Replace the
vague placeholder "- close" with a clear issue-close template such as "- close
`#이슈번호`" and add a short inline hint so authors know to replace "#이슈번호" with the
actual issue number (e.g., "- close #<issue-number>"). Update the template line
that currently contains "- close" to use this new default and ensure surrounding
PR template sections mention the expected format (요약 / 😎 해결한 이슈) so
contributors follow the `close `#이슈번호`` convention.