Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`vp migrate --full` asks to set up pre-commit hooks even when they're already configured

Open Beginner friendly
#3,096 0 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust

Research direction

Start by reading promptGitHooks() and the existing hasExistingViteHooksPolicy() check used by setupGitHooks(). Trace how vp migrate --full handles existing hooks and look for the relevant prompt tests. Done when existing Vite+ hooks are recognized and the user is no longer asked to set them up as if they were absent.

Written by the indexing model from the issue text.

Description

contribution welcome

Description

In a project that already has Vite+ hooks (.vite-hooks/pre-commit, core.hooksPath=.vite-hooks/_), vp migrate --full still asks:

◇ Set up pre-commit hooks to run formatting, linting, and type checking with auto-fixes?
  Yes / No

It defaults to Yes and doesn't say hooks already exist. Answering No sounds like it might disable them, though it doesn't.

The agent prompt in the same run detects the existing file and offers Append/Skip:

› Agent instructions already exist at AGENTS.md.
    Append
  › Skip: Leave existing file unchanged

promptGitHooks() doesn't check hasExistingViteHooksPolicy(), which setupGitHooks() already uses to leave the hook as it is.

Suggested solution

When existing Vite+ hooks are detected, either:

  • Skip the prompt and log Git hooks already configured, or
  • Say so in the prompt and offer Keep/Skip, like the agent prompt does.

Additional context

Validations

  • Read the Contributing Guidelines.
  • Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
  • Check that there isn't already an issue requesting the same feature.
Dominant language
Rust
Stars
6.3k
Forks
283
Avg merge
1d 11h
Merged PRs (30d)
200

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidzero-dev/vite-plus

All issues in voidzero-dev/vite-plus

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.