chore(husky): enhance husky pre-push message

[synuns]

• add branch naming guidelines message

Changes

Visuals

Checklist

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

Additional Discussion Points

Summary by CodeRabbit

• Documentation
  • 브랜치 이름 규칙에 대한 안내 메시지가 개선되었습니다.
  • SUBJECT는 소문자, 숫자, 하이픈만 사용해야 하고, ISSUENUMBER는 숫자만 포함해야 한다는 점을 명확하게 안내하여 사용자가 올바른 이름 규칙을 쉽게 준수할 수 있도록 했습니다.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a30d6aa

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

이 PR은 .husky/pre-push 파일에 추가적인 echo 문구를 추가하여 브랜치 네이밍 규칙에 대해 명확한 안내 메시지를 출력하도록 수정하였습니다. "SUBJECT"는 소문자(a-z), 숫자(0-9), 하이픈(-)만 허용하며, "ISSUENUMBER"는 숫자만 허용한다는 내용을 명시합니다. 공개 API 변경은 없습니다.

Changes

파일	변경 내역
.husky/pre-push	에코 문구 추가: SUBJECT는 소문자, 숫자, 하이픈만 포함, ISSUENUMBER는 숫자만 포함하도록 규칙 안내 문구 추가

Possibly related PRs

• docs: update CONTRIBUTING.md #69: 브랜치 네이밍 규칙 및 가이드라인에 관한 업데이트와 관련.
• chore(husky): add pre-push githook for branch naming convention #87: pre-push 훅 내 브랜치 네이밍 검증과 에러 메시지 개선 사항이 유사함.

Suggested labels

documentation

Suggested reviewers

• noahluftyang
• bae-sh
• heeji289
• hy57in
• kimdaeyeobbb
• developerjhp
• froggy1014
• SEMIN-97

Poem

나는 작은 토끼, 코드의 뒷발로 뛰네
에코 문구 속에 숨은 규칙을 노래해
소문자와 숫자, 하이픈의 멋진 조화
브랜치 이름이 빛나도록, 안내 메시지로 춤추네
변경된 메시지와 함께, 모두 환영해! 🐰🌟

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 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 f29fc2d and a30d6aa.

📒 Files selected for processing (1)

• .husky/pre-push (1 hunks)

🔇 Additional comments (1)

.husky/pre-push (1)

13-14: 브랜치 네이밍 규칙에 대한 명확한 가이드라인 추가 👍

사용자가 브랜치 이름을 작성할 때 따라야 할 형식에 대한 구체적인 안내를 추가하여 가독성과 사용성을 향상시켰습니다. 이러한 명확한 지침은 팀 내 일관된 브랜치 네이밍 규칙을 유지하는 데 도움이 될 것입니다.

---

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

🪧 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.
• @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.