Bug: During run init command, finish the git initialize process without question to user('Initialize a new git repository?')
Maintainers usually reply within 1 day
A pull request for this has already been merged.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bun, typescript
- Domain
- cli
Research direction
The issue points to the wxt init command and relates the behavior to PR #2620. Start by reading that PR and tracing the init command's Git initialization prompt. Reproduce with bunx wxt@latest init in a new folder, then confirm the command asks before initializing Git and only initializes after an affirmative response.
Written by the indexing model from the issue text.
Description
Describe the bug
In v0.21.5, a feature was released to ask users whether they want to initialize a git repository when running the wxt init command, and proceed with initialization only if they reply "yes."
However, I tried on local, the git repository was initialized automatically without asking the prompt.
Related PR: #2620
Reproduction
https://github.com/user-attachments/assets/077562b6-53ed-4348-b99e-80f0f1bce17d
Steps to reproduce
- create new folder
- check not to managed by git this folder
- run
bunx wxt@latest init - check
git statuscommand
System Info
System:
OS: macOS 15.5
CPU: (10) arm64 Apple M4
Memory: 110.84 MB / 24.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 24.7.0 - /opt/homebrew/bin/node
Yarn: 1.22.22 - /opt/homebrew/bin/yarn
npm: 11.5.1 - /opt/homebrew/bin/npm
pnpm: 10.33.0 - /opt/homebrew/bin/pnpm
bun: 1.3.14 - /Users/katsu/.bun/bin/bun
Browsers:
Chrome: 156.0.8078.48
Safari: 18.5
Used Package Manager
bun
Validations
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
- Dominant language
- TypeScript
- Stars
- 10.6k
- Forks
- 581
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 46
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wxt-dev/wxt
-
Docs: update wxt init GIF movie along with releasing PR #2699Possibly taken @nishu-murmu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
MV3 dev dynamic content script registration drops matchOriginAsFallbackPossibly taken @cookesan claimed this 124 days ago. Opencontribution welcome good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wxt-dev/wxt#2335 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wxt-dev/wxt#2303 · 3 comments ·
Maintainers usually reply within 1 day
-
Warning `Firefox requires `data_collection_permissions` for new extensions` during workflowsPossibly taken @suveshmoza claimed this 3 days ago. Openchore contribution welcome
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
contribution welcome pkg/wxt upstream
Difficulty 3/5 1-2 days Newbie friendliness 55/100
wxt-dev/wxt#2686 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:web p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Lets-Parley/Parley#912 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
wealthfolio/wealthfolio#2376 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
be-BOP-io-SA/be-BOP#2817 ·
Maintainers usually reply within 5 days
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
sno-ai/sno-station#149 · 1 comment ·
Maintainers usually reply within 1 day