Skip to content

docs: add husky init command to bun in setup guide #4497

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 30, 2025

Conversation

Marukome0743
Copy link
Contributor

@Marukome0743 Marukome0743 commented Jun 30, 2025

Description

Update local setup guide to include the husky init command for v9 and clarify installation commands for lower versions.

Documentation:

  • Add bunx husky init step for Husky v9 in the local-setup guide
  • Clarify using bunx husky install for Husky v8 or lower versions

Motivation and Context

Follow up #4488 and #4491.

Usage examples

bun add --dev husky

# husky@v9
bunx husky init
# husky@v8 or lower
bunx husky install

# Add commit message linting to commit-msg hook
echo "bunx commitlint --edit \$1" > .husky/commit-msg
# Windows users should use ` to escape dollar signs
echo "bunx commitlint --edit `$1" > .husky/commit-msg

How Has This Been Tested?

I have tested on my local PC.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@escapedcat escapedcat merged commit c0fe405 into conventional-changelog:master Jun 30, 2025
12 checks passed
@Marukome0743 Marukome0743 deleted the husky branch June 30, 2025 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants