juspay / juspay/shelly

Bug: installs husky but does not add 'pre-commit' or 'commit-msg' hooks

Open
#44 1 comment 1 reaction 2 assignees Claimed by @Harshita-Rupani29 View on GitHub
Dominant language
TypeScript
Stars
1
Forks
2
PR merge metrics
No merged PRs in 30d

Description

## 🐛 Bug Description

When running `shelly gh --force` or `shelly organize`, Shelly creates a `.husky` folder locally (visible in VS Code), but this folder is never committed to git and therefore doesn't appear on GitHub.

## 🔍 Current Behavior

1. Run `shelly gh --force` on the NeuroPulse project
2. `.husky` folder is created locally (visible in file explorer/VS Code)
3. Run `git status` - shows "nothing to commit, working tree clean"
4. Check GitHub repository - `.husky` folder is missing
5. `.gitignore` does NOT contain `.husky`, so it should be tracked

## ✅ Expected Behavior

The `.husky` folder should be:
1. Created locally by Shelly ✅ (working)
2. Added to git tracking ❌ (failing)
3. Committed to the repository ❌ (failing)
4. Visible on GitHub ❌ (failing)

## 🧪 Evidence

- **Local file system**: `.husky` folder exists
- **Git status**: `nothing to commit, working tree clean`
- **GitHub**: No `.husky` folder visible
- **`.gitignore`**: Does NOT contain `.husky` (so it should be tracked)

## 🔗 Repository Context

**Repository**: https://github.com/juspay/NeuroPulse
**Reference**: The juspay/neurolink repository correctly has a `.husky` folder in git

## 🤔 Suspected Issue

Shelly appears to be creating the `.husky` folder but not running `git add .husky` before committing other changes. This means the folder exists locally but is never staged for commit.

## 🛠️ Workaround

Manual fix after Shelly setup:
```bash
git add .husky
git commit -m "feat: add husky git hooks configuration"
git push

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.