How to avoid empty commit?

[SunilDSK]

Version

0.6.0

Details

I have a webapi project with environment specific appsettings.json file. I don't want the appsettings.Development.json to be committed or pushed(its already tracked). I have a pre-commit hook with one command - git reset appsettings.Development.json. When I have appsettings.Development.json as only file, the pre-commit is unstaging the appsettings.Development.json file, but it is also creating an empty commit with no files. How do I avoid the empty commit?

Steps to reproduce

• Step 1: Once dotnet husky is installed, run the command - $ dotnet husky add pre-commit -c "git reset appsettings.Development.json".
• Step 2: Then modify the file appsettings.Development.json.
• Step 3: Then stage the file and try to commit it
• Step 4: The git will unstage the appsettings.Development.json file and create an empty commit.

[alirezanet]

Hi @SunilDSK,
I don't see it as a bug since I didn't fully understand what do you expect Husky does for you?

if you wanna prevent commits if appsettings.Development.json is staged I would suggest to use the task-runner instead.

something like:
e.g pre-commit file

#!/bin/sh
. "$(dirname "$0")/_/husky.sh"

dotnet husky run -v --group "pre-commit"

task-runner.json

{
 "tasks": [
      {
         "name": "Verify staged files",
         "group": "pre-commit",
         "include": "appsettings.Development.json",
         "command": "cmd",
         "args": ["/c", "git reset appsettings.Development.json & exit 1", "${staged}"]
      }
]
}

This would automatically unstage the appsettings.Development.json file if it is staged and prevent the commits including this file.

also using taks-runner makes your console log prettier :)