[System]
You are a helpful assistant that answers strictly in JSON. Here's the JSON schema you must adhere to:
<schema>
{"$schema":"http://json-schema.org/draft-07/schema#","$id":"https://json.schemastore.org/huskyrc.json","additionalProperties":false,"definitions":{"hook":{"type":"string","x-intellij-language-injection":"Shell Script"}},"description":"Husky can prevent bad `git commit`, `git push` and more \ud83d\udc36 woof!","properties":{"$schema":{"type":"string"},"skipCI":{"title":"Skipping Git hooks installation.","type":"boolean","default":false},"hooks":{"title":"Git hooks.","type":"object","properties":{"applypatch-msg":{"$comment":"https://git-scm.com/docs/githooks#_applypatch_msg","$ref":"#/definitions/hook","description":"This hook is invoked by git-am. It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with a non-zero status causes git am to abort before applying the patch.\n\nThe hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format. It can also be used to refuse the commit after inspecting the message file.\n\nThe default applypatch-msg hook, when enabled, runs the commit-msg hook, if the latter is enabled.","x-intellij-html-description":"
This hook is invoked by git-am. It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with a non-zero status causes git am to abort before applying the patch.
\n
The hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format. It can also be used to refuse the commit after inspecting the message file.
\n
The default applypatch-msg hook, when enabled, runs the commit-msg hook, if the latter is enabled.
","markdownDescription":"This hook is invoked by [git-am](https://git-scm.com/docs/git-am). It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with a non-zero status causes `git am` to abort before applying the patch.\n\nThe hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format. It can also be used to refuse the commit after inspecting the message file.\n\nThe default **applypatch-msg** hook, when enabled, runs the **commit-msg** hook, if the latter is enabled."},"pre-applypatch":{"$comment":"https://git-scm.com/docs/githooks#_pre_applypatch","$ref":"#/definitions/hook","description":"This hook is invoked by git-am. It takes no parameter, and is invoked after the patch is applied, but before a commit is made.\n\nIf it exits with non-zero status, then the working tree will not be committed after applying the patch.\n\nIt can be used to inspect the current working tree and refuse to make a commit if it does not pass certain test.\n\nThe default pre-applypatch hook, when enabled, runs the pre-commit hook, if the latter is enabled.","x-intellij-html-description":"
This hook is invoked by git-am. It takes no parameter, and is invoked after the patch is applied, but before a commit is made.
\n
If it exits with non-zero status, then the working tree will not be committed after applying the patch.
\n
It can be used to inspect the current working tree and refuse to make a commit if it does not pass certain test.
\n
The default pre-applypatch hook, when enabled, runs the pre-commit hook, if the latter is enabled.
","markdownDescription":"This hook is invoked by [git-am](https://git-scm.com/docs/git-am). It takes no parameter, and is invoked after the patch is applied, but before a commit is made.\n\nIf it exits with non-zero status, then the working tree will not be committed after applying the patch.\n\nIt can be used to inspect the current working tree and refuse to make a commit if it does not pass certain test.\n\nThe default **pre-applypatch** hook, when enabled, runs the **pre-commit** hook, if the latter is enabled."},"post-applypatch":{"$comment":"https://git-scm.com/docs/githooks#_post_applypatch","$ref":"#/definitions/hook","description":"This hook is invoked by git-am. It takes no parameter, and is invoked after the patch is applied and a commit is made.\n\nThis hook is meant primarily for notification, and cannot affect the outcome of git am.","x-intellij-html-description":"
This hook is invoked by git-am. It takes no parameter, and is invoked after the patch is applied and a commit is made.
\n
This hook is meant primarily for notification, and cannot affect the outcome of git am.
","markdownDescription":"This hook is invoked by [git-am](https://git-scm.com/docs/git-am). It takes no parameter, and is invoked after the patch is applied and a commit is made.\n\nThis hook is meant primarily for notification, and cannot affect the outcome of `git am`."},"pre-commit":{"$comment":"https://git-scm.com/docs/githooks#_pre_commit","$ref":"#/definitions/hook","description":"This hook is invoked by git-commit, and can be bypassed with the --no-verify option. It takes no parameters, and is invoked before obtaining the proposed commit log message and making a commit. Exiting with a non-zero status from this script causes the git commit command to abort before creating a commit.\n\nThe default pre-commit hook, when enabled, catches introduction of lines with trailing whitespaces and aborts the commit when such a line is found.\n\nAll the git commit hooks are invoked with the environment variable GIT_EDITOR=: if the command will not bring up an editor to modify the commit message.\n\nThe default pre-commit hook, when enabled\u2014\u200band with the hooks.allownonascii config option unset or set to false\u2014\u200bprevents the use of non-ASCII filenames.","x-intellij-html-description":"
This hook is invoked by git-commit, and can be bypassed with the --no-verify option. It takes no parameters, and is invoked before obtaining the proposed commit log message and making a commit. Exiting with a non-zero status from this script causes the git commit command to abort before creating a commit.
\n
The default pre-commit hook, when enabled, catches introduction of lines with trailing whitespaces and aborts the commit when such a line is found.
\n
All the git commit hooks are invoked with the environment variable GIT_EDITOR=: if the command will not bring up an editor to modify the commit message.
\n
The default pre-commit hook, when enabled\u2014\u200band with the hooks.allownonascii config option unset or set to false\u2014\u200bprevents the use of non-ASCII filenames.
","markdownDescription":"This hook is invoked by [git-commit](https://git-scm.com/docs/git-commit), and can be bypassed with the `--no-verify` option. It takes no parameters, and is invoked before obtaining the proposed commit log message and making a commit. Exiting with a non-zero status from this script causes the `git commit` command to abort before creating a commit.\n\nThe default **pre-commit** hook, when enabled, catches introduction of lines with trailing whitespaces and aborts the commit when such a line is found.\n\nAll the `git commit` hooks are invoked with the environment variable `GIT_EDITOR=:` if the command will not bring up an editor to modify the commit message.\n\nThe default **pre-commit** hook, when enabled\u2014\u200band with the `hooks.allownonascii` config option unset or set to false\u2014\u200bprevents the use of non-ASCII filenames."},"prepare-commit-msg":{"$comment":"https://git-scm.com/docs/githooks#_prepare_commit_msg","$ref":"#/definitions/hook","description":"This hook is invoked by git-commit right after preparing the default log message, and before the editor is started.\n\nIt takes one to three parameters. The first is the name of the file that contains the commit log message. The second is the source of the commit message, and can be: message (if a -m or -F option was given); template (if a -t option was given or the configuration option commit.template is set); merge (if the commit is a merge or a .git/MERGE_MSG file exists); squash (if a .git/SQUASH_MSG file exists); or commit, followed by a commit SHA-1 (if a -c, -C or --amend option was given).\n\nIf the exit status is non-zero, git commit will abort.\n\nThe purpose of the hook is to edit the message file in place, and it is not suppressed by the --no-verify option. A non-zero exit means a failure of the hook and aborts the commit. It should not be used as replacement for pre-commit hook.\n\nThe sample prepare-commit-msg hook that comes with Git removes the help message found in the commented portion of the commit template.","x-intellij-html-description":"
This hook is invoked by git-commit right after preparing the default log message, and before the editor is started.
\n
It takes one to three parameters. The first is the name of the file that contains the commit log message. The second is the source of the commit message, and can be: message (if a -m or -F option was given); template (if a -t option was given or the configuration option commit.template is set); merge (if the commit is a merge or a .git/MERGE_MSG file exists); squash (if a .git/SQUASH_MSG file exists); or commit, followed by a commit SHA-1 (if a -c, -C or --amend option was given).
\n
If the exit status is non-zero, git commit will abort.
\n
The purpose of the hook is to edit the message file in place, and it is not suppressed by the --no-verify option. A non-zero exit means a failure of the hook and aborts the commit. It should not be used as replacement for pre-commit hook.
\n
The sample prepare-commit-msg hook that comes with Git removes the help message found in the commented portion of the commit template.
","markdownDescription":"This hook is invoked by [git-commit](https://git-scm.com/docs/git-commit) right after preparing the default log message, and before the editor is started.\n\nIt takes one to three parameters. The first is the name of the file that contains the commit log message. The second is the source of the commit message, and can be: `message` (if a `-m` or `-F` option was given); `template` (if a `-t` option was given or the configuration option `commit.template` is set); `merge` (if the commit is a merge or a `.git/MERGE_MSG` file exists); `squash` (if a `.git/SQUASH_MSG` file exists); or `commit`, followed by a commit SHA-1 (if a `-c`, `-C` or `--amend` option was given).\n\nIf the exit status is non-zero, `git commit` will abort.\n\nThe purpose of the hook is to edit the message file in place, and it is not suppressed by the `--no-verify` option. A non-zero exit means a failure of the hook and aborts the commit. It should not be used as replacement for pre-commit hook.\n\nThe sample `prepare-commit-msg` hook that comes with Git removes the help message found in the commented portion of the commit template."},"commit-msg":{"$comment":"https://git-scm.com/docs/githooks#_commit_msg","$ref":"#/definitions/hook","description":"This hook is invoked by git-commit and git-merge, and can be bypassed with the --no-verify option. It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with a non-zero status causes the command to abort.\n\nThe hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format. It can also be used to refuse the commit after inspecting the message file.\n\nThe default commit-msg hook, when enabled, detects duplicate \"Signed-off-by\" lines, and aborts the commit if one is found.","x-intellij-html-description":"
This hook is invoked by git-commit and git-merge, and can be bypassed with the --no-verify option. It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with a non-zero status causes the command to abort.
\n
The hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format. It can also be used to refuse the commit after inspecting the message file.
\n
The default commit-msg hook, when enabled, detects duplicate \"Signed-off-by\" lines, and aborts the commit if one is found.
","markdownDescription":"This hook is invoked by [git-commit](https://git-scm.com/docs/git-commit) and [git-merge](https://git-scm.com/docs/git-merge), and can be bypassed with the `--no-verify` option. It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with a non-zero status causes the command to abort.\n\nThe hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format. It can also be used to refuse the commit after inspecting the message file.\n\nThe default **commit-msg** hook, when enabled, detects duplicate \"Signed-off-by\" lines, and aborts the commit if one is found."},"post-commit":{"$comment":"https://git-scm.com/docs/githooks#_post_commit","$ref":"#/definitions/hook","description":"This hook is invoked by git-commit. It takes no parameters, and is invoked after a commit is made.\n\nThis hook is meant primarily for notification, and cannot affect the outcome of git commit.","x-intellij-html-description":"
This hook is invoked by git-commit. It takes no parameters, and is invoked after a commit is made.
\n
This hook is meant primarily for notification, and cannot affect the outcome of git commit.
","markdownDescription":"This hook is invoked by [git-commit](https://git-scm.com/docs/git-commit). It takes no parameters, and is invoked after a commit is made.\n\nThis hook is meant primarily for notification, and cannot affect the outcome of `git commit`."},"pre-rebase":{"$comment":"https://git-scm.com/docs/githooks#_pre_rebase","$ref":"#/definitions/hook","description":"This hook is called by git-rebase and can be used to prevent a branch from getting rebased. The hook may be called with one or two parameters. The first parameter is the upstream from which the series was forked. The second parameter is the branch being rebased, and is not set when rebasing the current branch.","x-intellij-html-description":"
This hook is called by git-rebase and can be used to prevent a branch from getting rebased. The hook may be called with one or two parameters. The first parameter is the upstream from which the series was forked. The second parameter is the branch being rebased, and is not set when rebasing the current branch.
","markdownDescription":"This hook is called by [git-rebase](https://git-scm.com/docs/git-rebase) and can be used to prevent a branch from getting rebased. The hook may be called with one or two parameters. The first parameter is the upstream from which the series was forked. The second parameter is the branch being rebased, and is not set when rebasing the current branch."},"post-checkout":{"$comment":"https://git-scm.com/docs/githooks#_post_checkout","$ref":"#/definitions/hook","description":"This hook is invoked when a git-checkout or git-switch is run after having updated the worktree. The hook is given three parameters: the ref of the previous HEAD, the ref of the new HEAD (which may or may not have changed), and a flag indicating whether the checkout was a branch checkout (changing branches, flag=1) or a file checkout (retrieving a file from the index, flag=0). This hook cannot affect the outcome of git switch or git checkout.\n\nIt is also run after git-clone, unless the --no-checkout (-n) option is used. The first parameter given to the hook is the null-ref, the second the ref of the new HEAD and the flag is always 1. Likewise for git worktree add unless --no-checkout is used.\n\nThis hook can be used to perform repository validity checks, auto-display differences from the previous HEAD if different, or set working dir metadata properties.","x-intellij-html-description":"
This hook is invoked when a git-checkout or git-switch is run after having updated the worktree. The hook is given three parameters: the ref of the previous HEAD, the ref of the new HEAD (which may or may not have changed), and a flag indicating whether the checkout was a branch checkout (changing branches, flag=1) or a file checkout (retrieving a file from the index, flag=0). This hook cannot affect the outcome of git switch or git checkout.
\n
It is also run after git-clone, unless the --no-checkout (-n) option is used. The first parameter given to the hook is the null-ref, the second the ref of the new HEAD and the flag is always 1. Likewise for git worktree add unless --no-checkout is used.
\n
This hook can be used to perform repository validity checks, auto-display differences from the previous HEAD if different, or set working dir metadata properties.
","markdownDescription":"This hook is invoked when a [git-checkout](https://git-scm.com/docs/git-checkout) or [git-switch](https://git-scm.com/docs/git-switch) is run after having updated the worktree. The hook is given three parameters: the ref of the previous HEAD, the ref of the new HEAD (which may or may not have changed), and a flag indicating whether the checkout was a branch checkout (changing branches, flag=1) or a file checkout (retrieving a file from the index, flag=0). This hook cannot affect the outcome of `git switch` or `git checkout`.\n\nIt is also run after [git-clone](https://git-scm.com/docs/git-clone), unless the `--no-checkout` (`-n`) option is used. The first parameter given to the hook is the null-ref, the second the ref of the new HEAD and the flag is always 1. Likewise for `git worktree add` unless `--no-checkout` is used.\n\nThis hook can be used to perform repository validity checks, auto-display differences from the previous HEAD if different, or set working dir metadata properties."},"post-merge":{"$comment":"https://git-scm.com/docs/githooks#_post_merge","$ref":"#/definitions/hook","description":"This hook is invoked by git-merge, which happens when a git pull is done on a local repository. The hook takes a single parameter, a status flag specifying whether or not the merge being done was a squash merge. This hook cannot affect the outcome of git merge and is not executed, if the merge failed due to conflicts.\n\nThis hook can be used in conjunction with a corresponding pre-commit hook to save and restore any form of metadata associated with the working tree (e.g.: permissions/ownership, ACLS, etc). See contrib/hooks/setgitperms.perl for an example of how to do this.","x-intellij-html-description":"
This hook is invoked by git-merge, which happens when a git pull is done on a local repository. The hook takes a single parameter, a status flag specifying whether or not the merge being done was a squash merge. This hook cannot affect the outcome of git merge and is not executed, if the merge failed due to conflicts.
\n
This hook can be used in conjunction with a corresponding pre-commit hook to save and restore any form of metadata associated with the working tree (e.g.: permissions/ownership, ACLS, etc). See contrib/hooks/setgitperms.perl for an example of how to do this.
","markdownDescription":"This hook is invoked by [git-merge](https://git-scm.com/docs/git-merge), which happens when a `git pull` is done on a local repository. The hook takes a single parameter, a status flag specifying whether or not the merge being done was a squash merge. This hook cannot affect the outcome of `git merge` and is not executed, if the merge failed due to conflicts.\n\nThis hook can be used in conjunction with a corresponding pre-commit hook to save and restore any form of metadata associated with the working tree (e.g.: permissions/ownership, ACLS, etc). See contrib/hooks/setgitperms.perl for an example of how to do this."},"pre-push":{"$comment":"https://git-scm.com/docs/githooks#_pre_push","$ref":"#/definitions/hook","description":"This hook is called by git-push and can be used to prevent a push from taking place. The hook is called with two parameters which provide the name and location of the destination remote, if a named remote is not being used both values will be the same.\n\nInformation about what is to be pushed is provided on the hook's standard input with lines of the form:\n\n<local ref> SP <local sha1> SP <remote ref> SP <remote sha1> LF\nFor instance, if the command git push origin master:foreign were run the hook would receive a line like the following:\n\nrefs/heads/master 67890 refs/heads/foreign 12345\nalthough the full, 40-character SHA-1s would be supplied. If the foreign ref does not yet exist the <remote SHA-1> will be 40 0. If a ref is to be deleted, the <local ref> will be supplied as (delete) and the <local SHA-1> will be 40 0. If the local commit was specified by something other than a name which could be expanded (such as HEAD~, or a SHA-1) it will be supplied as it was originally given.\n\nIf this hook exits with a non-zero status, git push will abort without pushing anything. Information about why the push is rejected may be sent to the user by writing to standard error.","x-intellij-html-description":"
This hook is called by git-push and can be used to prevent a push from taking place. The hook is called with two parameters which provide the name and location of the destination remote, if a named remote is not being used both values will be the same.
\n
Information about what is to be pushed is provided on the hook's standard input with lines of the form:
\n
<local ref> SP <local sha1> SP <remote ref> SP <remote sha1> LF
\n
For instance, if the command git push origin master:foreign were run the hook would receive a line like the following:
\n
refs/heads/master 67890 refs/heads/foreign 12345
\n
although the full, 40-character SHA-1s would be supplied. If the foreign ref does not yet exist the <remote SHA-1> will be 40 0. If a ref is to be deleted, the <local ref> will be supplied as (delete) and the <local SHA-1> will be 40 0. If the local commit was specified by something other than a name which could be expanded (such as HEAD~, or a SHA-1) it will be supplied as it was originally given.
\n
If this hook exits with a non-zero status, git push will abort without pushing anything. Information about why the push is rejected may be sent to the user by writing to standard error.
","markdownDescription":"This hook is called by [git-push](https://git-scm.com/docs/git-push) and can be used to prevent a push from taking place. The hook is called with two parameters which provide the name and location of the destination remote, if a named remote is not being used both values will be the same.\n\nInformation about what is to be pushed is provided on the hook's standard input with lines of the form:\n```\n<local ref> SP <local sha1> SP <remote ref> SP <remote sha1> LF\n```\nFor instance, if the command `git push origin master:foreign` were run the hook would receive a line like the following:\n```\nrefs/heads/master 67890 refs/heads/foreign 12345\n```\nalthough the full, 40-character SHA-1s would be supplied. If the foreign ref does not yet exist the `<remote SHA-1>` will be 40 `0`. If a ref is to be deleted, the `<local ref>` will be supplied as `(delete)` and the `<local SHA-1>` will be 40 `0`. If the local commit was specified by something other than a name which could be expanded (such as `HEAD~`, or a SHA-1) it will be supplied as it was originally given.\n\nIf this hook exits with a non-zero status, `git push` will abort without pushing anything. Information about why the push is rejected may be sent to the user by writing to standard error."},"post-update":{"$comment":"https://git-scm.com/docs/githooks#_post_update","$ref":"#/definitions/hook","description":"This hook is invoked by git-receive-pack when it reacts to git push and updates reference(s) in its repository. It executes on the remote repository once after all the refs have been updated.\n\nIt takes a variable number of parameters, each of which is the name of ref that was actually updated.\n\nThis hook is meant primarily for notification, and cannot affect the outcome of git receive-pack.\n\nThe post-update hook can tell what are the heads that were pushed, but it does not know what their original and updated values are, so it is a poor place to do log old..new. The post-receive hook does get both original and updated values of the refs. You might consider it instead if you need them.\n\nWhen enabled, the default post-update hook runs git update-server-info to keep the information used by dumb transports (e.g., HTTP) up to date. If you are publishing a Git repository that is accessible via HTTP, you should probably enable this hook.\n\nBoth standard output and standard error output are forwarded to git send-pack on the other end, so you can simply echo messages for the user.","x-intellij-html-description":"
This hook is invoked by git-receive-pack when it reacts to git push and updates reference(s) in its repository. It executes on the remote repository once after all the refs have been updated.
\n
It takes a variable number of parameters, each of which is the name of ref that was actually updated.
\n
This hook is meant primarily for notification, and cannot affect the outcome of git receive-pack.
\n
The post-update hook can tell what are the heads that were pushed, but it does not know what their original and updated values are, so it is a poor place to do log old..new. The post-receive hook does get both original and updated values of the refs. You might consider it instead if you need them.
\n
When enabled, the default post-update hook runs git update-server-info to keep the information used by dumb transports (e.g., HTTP) up to date. If you are publishing a Git repository that is accessible via HTTP, you should probably enable this hook.
\n
Both standard output and standard error output are forwarded to git send-pack on the other end, so you can simply echo messages for the user.
","markdownDescription":"This hook is invoked by [git-receive-pack](https://git-scm.com/docs/git-receive-pack) when it reacts to `git push` and updates reference(s) in its repository. It executes on the remote repository once after all the refs have been updated.\n\nIt takes a variable number of parameters, each of which is the name of ref that was actually updated.\n\nThis hook is meant primarily for notification, and cannot affect the outcome of `git receive-pack`.\n\nThe **post-update** hook can tell what are the heads that were pushed, but it does not know what their original and updated values are, so it is a poor place to do log old..new. The **post-receive** hook does get both original and updated values of the refs. You might consider it instead if you need them.\n\nWhen enabled, the default **post-update** hook runs `git update-server-info` to keep the information used by dumb transports (e.g., HTTP) up to date. If you are publishing a Git repository that is accessible via HTTP, you should probably enable this hook.\n\nBoth standard output and standard error output are forwarded to `git send-pack` on the other end, so you can simply `echo` messages for the user."},"push-to-checkout":{"$comment":"https://git-scm.com/docs/githooks#_push_to_checkout","$ref":"#/definitions/hook","description":"This hook is invoked by git-receive-pack when it reacts to git push and updates reference(s) in its repository, and when the push tries to update the branch that is currently checked out and the receive.denyCurrentBranch configuration variable is set to updateInstead. Such a push by default is refused if the working tree and the index of the remote repository has any difference from the currently checked out commit; when both the working tree and the index match the current commit, they are updated to match the newly pushed tip of the branch. This hook is to be used to override the default behaviour.\n\nThe hook receives the commit with which the tip of the current branch is going to be updated. It can exit with a non-zero status to refuse the push (when it does so, it must not modify the index or the working tree). Or it can make any necessary changes to the working tree and to the index to bring them to the desired state when the tip of the current branch is updated to the new commit, and exit with a zero status.\n\nFor example, the hook can simply run git read-tree -u -m HEAD \"$1\" in order to emulate git fetch that is run in the reverse direction with git push, as the two-tree form of git read-tree -u -m is essentially the same as git switch or git checkout that switches branches while keeping the local changes in the working tree that do not interfere with the difference between the branches.","x-intellij-html-description":"
This hook is invoked by git-receive-pack when it reacts to git push and updates reference(s) in its repository, and when the push tries to update the branch that is currently checked out and the receive.denyCurrentBranch configuration variable is set to updateInstead. Such a push by default is refused if the working tree and the index of the remote repository has any difference from the currently checked out commit; when both the working tree and the index match the current commit, they are updated to match the newly pushed tip of the branch. This hook is to be used to override the default behaviour.
\n
The hook receives the commit with which the tip of the current branch is going to be updated. It can exit with a non-zero status to refuse the push (when it does so, it must not modify the index or the working tree). Or it can make any necessary changes to the working tree and to the index to bring them to the desired state when the tip of the current branch is updated to the new commit, and exit with a zero status.
\n
For example, the hook can simply run git read-tree -u -m HEAD \"$1\" in order to emulate git fetch that is run in the reverse direction with git push, as the two-tree form of git read-tree -u -m is essentially the same as git switch or git checkout that switches branches while keeping the local changes in the working tree that do not interfere with the difference between the branches.
","markdownDescription":"This hook is invoked by [git-receive-pack](https://git-scm.com/docs/git-receive-pack) when it reacts to `git push` and updates reference(s) in its repository, and when the push tries to update the branch that is currently checked out and the `receive.denyCurrentBranch` configuration variable is set to `updateInstead`. Such a push by default is refused if the working tree and the index of the remote repository has any difference from the currently checked out commit; when both the working tree and the index match the current commit, they are updated to match the newly pushed tip of the branch. This hook is to be used to override the default behaviour.\n\nThe hook receives the commit with which the tip of the current branch is going to be updated. It can exit with a non-zero status to refuse the push (when it does so, it must not modify the index or the working tree). Or it can make any necessary changes to the working tree and to the index to bring them to the desired state when the tip of the current branch is updated to the new commit, and exit with a zero status.\n\nFor example, the hook can simply run `git read-tree -u -m HEAD \"$1\"` in order to emulate `git fetch` that is run in the reverse direction with `git push`, as the two-tree form of `git read-tree -u -m` is essentially the same as `git switch` or `git checkout` that switches branches while keeping the local changes in the working tree that do not interfere with the difference between the branches."},"pre-auto-gc":{"$comment":"https://git-scm.com/docs/githooks#_pre_auto_gc","$ref":"#/definitions/hook","description":"This hook is invoked by git gc --auto (see git-gc). It takes no parameter, and exiting with non-zero status from this script causes the git gc --auto to abort.","x-intellij-html-description":"
This hook is invoked by git gc --auto (see git-gc). It takes no parameter, and exiting with non-zero status from this script causes the git gc --auto to abort.
","markdownDescription":"This hook is invoked by `git gc --auto` (see [git-gc](https://git-scm.com/docs/git-gc)). It takes no parameter, and exiting with non-zero status from this script causes the `git gc --auto` to abort."},"post-rewrite":{"$comment":"https://git-scm.com/docs/githooks#_post_rewrite","$ref":"#/definitions/hook","description":"This hook is invoked by commands that rewrite commits (git-commit when called with --amend and git-rebase; however, full-history (re)writing tools like git-fast-import or git-filter-repo typically do not call it!). Its first argument denotes the command it was invoked by: currently one of amend or rebase. Further command-dependent arguments may be passed in the future.\n\nThe hook receives a list of the rewritten commits on stdin, in the format\n\n<old-sha1> SP <new-sha1> [ SP <extra-info> ] LF\nThe extra-info is again command-dependent. If it is empty, the preceding SP is also omitted. Currently, no commands pass any extra-info.\n\nThe hook always runs after the automatic note copying (see \"notes.rewrite.<command>\" in git-config) has happened, and thus has access to these notes.\n\nThe following command-specific comments apply:\n\nrebase\nFor the squash and fixup operation, all commits that were squashed are listed as being rewritten to the squashed commit. This means that there will be several lines sharing the same new-sha1.\n\nThe commits are guaranteed to be listed in the order that they were processed by rebase.","x-intellij-html-description":"
This hook is invoked by commands that rewrite commits (git-commit when called with --amend and git-rebase; however, full-history (re)writing tools like git-fast-import or git-filter-repo typically do not call it!). Its first argument denotes the command it was invoked by: currently one of amend or rebase. Further command-dependent arguments may be passed in the future.
\n
The hook receives a list of the rewritten commits on stdin, in the format
\n
<old-sha1> SP <new-sha1> [ SP <extra-info> ] LF
\n
The extra-info is again command-dependent. If it is empty, the preceding SP is also omitted. Currently, no commands pass any extra-info.
\n
The hook always runs after the automatic note copying (see \"notes.rewrite.<command>\" in git-config) has happened, and thus has access to these notes.
\n
The following command-specific comments apply:
\n
\n
rebase
\n
\n
For the squash and fixup operation, all commits that were squashed are listed as being rewritten to the squashed commit. This means that there will be several lines sharing the same new-sha1.
\n
The commits are guaranteed to be listed in the order that they were processed by rebase.
\n
\n
","markdownDescription":"This hook is invoked by commands that rewrite commits ([git-commit](https://git-scm.com/docs/git-commit) when called with `--amend` and [git-rebase](https://git-scm.com/docs/git-rebase); however, full-history (re)writing tools like [git-fast-import](https://git-scm.com/docs/git-fast-import) or [git-filter-repo](https://github.com/newren/git-filter-repo) typically do not call it!). Its first argument denotes the command it was invoked by: currently one of `amend` or `rebase`. Further command-dependent arguments may be passed in the future.\n\nThe hook receives a list of the rewritten commits on stdin, in the format\n```\n<old-sha1> SP <new-sha1> [ SP <extra-info> ] LF\n```\nThe **extra-info** is again command-dependent. If it is empty, the preceding SP is also omitted. Currently, no commands pass any **extra-info**.\n\nThe hook always runs after the automatic note copying (see \"notes.rewrite.\\<command\\>\" in [git-config](https://git-scm.com/docs/git-config)) has happened, and thus has access to these notes.\n\nThe following command-specific comments apply:\n\n**rebase**  \nFor the **squash** and **fixup** operation, all commits that were squashed are listed as being rewritten to the squashed commit. This means that there will be several lines sharing the same **new-sha1**.  \nThe commits are guaranteed to be listed in the order that they were processed by rebase."},"sendemail-validate":{"$comment":"https://git-scm.com/docs/githooks#_sendemail_validate","$ref":"#/definitions/hook","description":"This hook is invoked by git-send-email. It takes a single parameter, the name of the file that holds the e-mail to be sent. Exiting with a non-zero status causes git send-email to abort before sending any e-mails.","x-intellij-html-description":"
This hook is invoked by git-send-email. It takes a single parameter, the name of the file that holds the e-mail to be sent. Exiting with a non-zero status causes git send-email to abort before sending any e-mails.
","markdownDescription":"This hook is invoked by [git-send-email](https://git-scm.com/docs/git-send-email). It takes a single parameter, the name of the file that holds the e-mail to be sent. Exiting with a non-zero status causes `git send-email` to abort before sending any e-mails."},"fsmonitor-watchman":{"$comment":"https://git-scm.com/docs/githooks#_fsmonitor_watchman","$ref":"#/definitions/hook","description":"This hook is invoked when the configuration option core.fsmonitor is set to .git/hooks/fsmonitor-watchman. It takes two arguments, a version (currently 1) and the time in elapsed nanoseconds since midnight, January 1, 1970.\n\nThe hook should output to stdout the list of all files in the working directory that may have changed since the requested time. The logic should be inclusive so that it does not miss any potential changes. The paths should be relative to the root of the working directory and be separated by a single NUL.\n\nIt is OK to include files which have not actually changed. All changes including newly-created and deleted files should be included. When files are renamed, both the old and the new name should be included.\n\nGit will limit what files it checks for changes as well as which directories are checked for untracked files based on the path names given.\n\nAn optimized way to tell git \"all files have changed\" is to return the filename /.\n\nThe exit status determines whether git will use the data from the hook to limit its search. On error, it will fall back to verifying all files and folders.","x-intellij-html-description":"
This hook is invoked when the configuration option core.fsmonitor is set to .git/hooks/fsmonitor-watchman or .git/hooks/fsmonitor-watchmanv2 depending on the version of the hook to use.
\n
Version 1 takes two arguments, a version (1) and the time in elapsed nanoseconds since midnight, January 1, 1970.
\n
Version 2 takes two arguments, a version (2) and a token that is used for identifying changes since the token. For watchman this would be a clock id. This version must output to stdout the new token followed by a NUL before the list of files.
\n
The hook should output to stdout the list of all files in the working directory that may have changed since the requested time. The logic should be inclusive so that it does not miss any potential changes. The paths should be relative to the root of the working directory and be separated by a single NUL.
\n
It is OK to include files which have not actually changed. All changes including newly-created and deleted files should be included. When files are renamed, both the old and the new name should be included.
\n
Git will limit what files it checks for changes as well as which directories are checked for untracked files based on the path names given.
\n
An optimized way to tell git \"all files have changed\" is to return the filename /.
\n
The exit status determines whether git will use the data from the hook to limit its search. On error, it will fall back to verifying all files and folders.
","markdownDescription":"This hook is invoked when the configuration option `core.fsmonitor` is set to `.git/hooks/fsmonitor-watchman`. It takes two arguments, a version (currently 1) and the time in elapsed nanoseconds since midnight, January 1, 1970.\n\nThe hook should output to stdout the list of all files in the working directory that may have changed since the requested time. The logic should be inclusive so that it does not miss any potential changes. The paths should be relative to the root of the working directory and be separated by a single NUL.\n\nIt is OK to include files which have not actually changed. All changes including newly-created and deleted files should be included. When files are renamed, both the old and the new name should be included.\n\nGit will limit what files it checks for changes as well as which directories are checked for untracked files based on the path names given.\n\nAn optimized way to tell git \"all files have changed\" is to return the filename `/`.\n\nThe exit status determines whether git will use the data from the hook to limit its search. On error, it will fall back to verifying all files and folders."},"p4-pre-submit":{"$comment":"https://git-scm.com/docs/githooks#_p4_pre_submit","$ref":"#/definitions/hook","description":"This hook is invoked by git-p4 submit. It takes no parameters and nothing from standard input. Exiting with non-zero status from this script prevent git-p4 submit from launching. Run git-p4 submit --help for details.","x-intellij-html-description":"
This hook is invoked by git-p4 submit. It takes no parameters and nothing from standard input. Exiting with non-zero status from this script prevent git-p4 submit from launching. Run git-p4 submit --help for details.
","markdownDescription":"This hook is invoked by `git-p4 submit`. It takes no parameters and nothing from standard input. Exiting with non-zero status from this script prevent `git-p4 submit` from launching. Run `git-p4 submit --help` for details."}},"additionalProperties":false}},"required":["hooks"],"title":"Husky configuration.","type":"object"}
</schema>

[User] Provide a JSON object that satisfies the schema "Husky configuration.". Here are the required top‑level fields: hooks. Return only the valid JSON object.

Husky can prevent bad `git commit`, `git push` and more 🐶 woof!

Skipping Git hooks installation.

Git hooks.

This hook is invoked by git-am. It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with a non-zero status causes git am to abort before applying the patch.

The hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format. It can also be used to refuse the commit after inspecting the message file.

The default applypatch-msg hook, when enabled, runs the commit-msg hook, if the latter is enabled.

This hook is invoked by [git-am](https://git-scm.com/docs/git-am). It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with a non-zero status causes `git am` to abort before applying the patch.

The hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format. It can also be used to refuse the commit after inspecting the message file.

The default **applypatch-msg** hook, when enabled, runs the **commit-msg** hook, if the latter is enabled.

This hook is invoked by git-am. It takes no parameter, and is invoked after the patch is applied, but before a commit is made.

If it exits with non-zero status, then the working tree will not be committed after applying the patch.

It can be used to inspect the current working tree and refuse to make a commit if it does not pass certain test.

The default pre-applypatch hook, when enabled, runs the pre-commit hook, if the latter is enabled.

This hook is invoked by [git-am](https://git-scm.com/docs/git-am). It takes no parameter, and is invoked after the patch is applied, but before a commit is made.

If it exits with non-zero status, then the working tree will not be committed after applying the patch.

It can be used to inspect the current working tree and refuse to make a commit if it does not pass certain test.

The default **pre-applypatch** hook, when enabled, runs the **pre-commit** hook, if the latter is enabled.

This hook is invoked by git-am. It takes no parameter, and is invoked after the patch is applied and a commit is made.

This hook is meant primarily for notification, and cannot affect the outcome of git am.

This hook is invoked by [git-am](https://git-scm.com/docs/git-am). It takes no parameter, and is invoked after the patch is applied and a commit is made.

This hook is meant primarily for notification, and cannot affect the outcome of `git am`.

This hook is invoked by git-commit, and can be bypassed with the --no-verify option. It takes no parameters, and is invoked before obtaining the proposed commit log message and making a commit. Exiting with a non-zero status from this script causes the git commit command to abort before creating a commit.

The default pre-commit hook, when enabled, catches introduction of lines with trailing whitespaces and aborts the commit when such a line is found.

All the git commit hooks are invoked with the environment variable GIT_EDITOR=: if the command will not bring up an editor to modify the commit message.

The default pre-commit hook, when enabled—and with the hooks.allownonascii config option unset or set to false—prevents the use of non-ASCII filenames.

This hook is invoked by [git-commit](https://git-scm.com/docs/git-commit), and can be bypassed with the `--no-verify` option. It takes no parameters, and is invoked before obtaining the proposed commit log message and making a commit. Exiting with a non-zero status from this script causes the `git commit` command to abort before creating a commit.

The default **pre-commit** hook, when enabled, catches introduction of lines with trailing whitespaces and aborts the commit when such a line is found.

All the `git commit` hooks are invoked with the environment variable `GIT_EDITOR=:` if the command will not bring up an editor to modify the commit message.

The default **pre-commit** hook, when enabled—and with the `hooks.allownonascii` config option unset or set to false—prevents the use of non-ASCII filenames.

This hook is invoked by git-commit right after preparing the default log message, and before the editor is started.

It takes one to three parameters. The first is the name of the file that contains the commit log message. The second is the source of the commit message, and can be: message (if a -m or -F option was given); template (if a -t option was given or the configuration option commit.template is set); merge (if the commit is a merge or a .git/MERGE_MSG file exists); squash (if a .git/SQUASH_MSG file exists); or commit, followed by a commit SHA-1 (if a -c, -C or --amend option was given).

If the exit status is non-zero, git commit will abort.

The purpose of the hook is to edit the message file in place, and it is not suppressed by the --no-verify option. A non-zero exit means a failure of the hook and aborts the commit. It should not be used as replacement for pre-commit hook.

The sample prepare-commit-msg hook that comes with Git removes the help message found in the commented portion of the commit template.

This hook is invoked by [git-commit](https://git-scm.com/docs/git-commit) right after preparing the default log message, and before the editor is started.

It takes one to three parameters. The first is the name of the file that contains the commit log message. The second is the source of the commit message, and can be: `message` (if a `-m` or `-F` option was given); `template` (if a `-t` option was given or the configuration option `commit.template` is set); `merge` (if the commit is a merge or a `.git/MERGE_MSG` file exists); `squash` (if a `.git/SQUASH_MSG` file exists); or `commit`, followed by a commit SHA-1 (if a `-c`, `-C` or `--amend` option was given).

If the exit status is non-zero, `git commit` will abort.

The purpose of the hook is to edit the message file in place, and it is not suppressed by the `--no-verify` option. A non-zero exit means a failure of the hook and aborts the commit. It should not be used as replacement for pre-commit hook.

The sample `prepare-commit-msg` hook that comes with Git removes the help message found in the commented portion of the commit template.

This hook is invoked by git-commit and git-merge, and can be bypassed with the --no-verify option. It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with a non-zero status causes the command to abort.

The hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format. It can also be used to refuse the commit after inspecting the message file.

The default commit-msg hook, when enabled, detects duplicate "Signed-off-by" lines, and aborts the commit if one is found.

This hook is invoked by [git-commit](https://git-scm.com/docs/git-commit) and [git-merge](https://git-scm.com/docs/git-merge), and can be bypassed with the `--no-verify` option. It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with a non-zero status causes the command to abort.

The hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format. It can also be used to refuse the commit after inspecting the message file.

The default **commit-msg** hook, when enabled, detects duplicate "Signed-off-by" lines, and aborts the commit if one is found.

This hook is invoked by git-commit. It takes no parameters, and is invoked after a commit is made.

This hook is meant primarily for notification, and cannot affect the outcome of git commit.

This hook is invoked by [git-commit](https://git-scm.com/docs/git-commit). It takes no parameters, and is invoked after a commit is made.

This hook is meant primarily for notification, and cannot affect the outcome of `git commit`.

This hook is called by git-rebase and can be used to prevent a branch from getting rebased. The hook may be called with one or two parameters. The first parameter is the upstream from which the series was forked. The second parameter is the branch being rebased, and is not set when rebasing the current branch.

This hook is called by [git-rebase](https://git-scm.com/docs/git-rebase) and can be used to prevent a branch from getting rebased. The hook may be called with one or two parameters. The first parameter is the upstream from which the series was forked. The second parameter is the branch being rebased, and is not set when rebasing the current branch.

This hook is invoked when a git-checkout or git-switch is run after having updated the worktree. The hook is given three parameters: the ref of the previous HEAD, the ref of the new HEAD (which may or may not have changed), and a flag indicating whether the checkout was a branch checkout (changing branches, flag=1) or a file checkout (retrieving a file from the index, flag=0). This hook cannot affect the outcome of git switch or git checkout.

It is also run after git-clone, unless the --no-checkout (-n) option is used. The first parameter given to the hook is the null-ref, the second the ref of the new HEAD and the flag is always 1. Likewise for git worktree add unless --no-checkout is used.

This hook can be used to perform repository validity checks, auto-display differences from the previous HEAD if different, or set working dir metadata properties.

This hook is invoked when a [git-checkout](https://git-scm.com/docs/git-checkout) or [git-switch](https://git-scm.com/docs/git-switch) is run after having updated the worktree. The hook is given three parameters: the ref of the previous HEAD, the ref of the new HEAD (which may or may not have changed), and a flag indicating whether the checkout was a branch checkout (changing branches, flag=1) or a file checkout (retrieving a file from the index, flag=0). This hook cannot affect the outcome of `git switch` or `git checkout`.

It is also run after [git-clone](https://git-scm.com/docs/git-clone), unless the `--no-checkout` (`-n`) option is used. The first parameter given to the hook is the null-ref, the second the ref of the new HEAD and the flag is always 1. Likewise for `git worktree add` unless `--no-checkout` is used.

This hook can be used to perform repository validity checks, auto-display differences from the previous HEAD if different, or set working dir metadata properties.

This hook is invoked by git-merge, which happens when a git pull is done on a local repository. The hook takes a single parameter, a status flag specifying whether or not the merge being done was a squash merge. This hook cannot affect the outcome of git merge and is not executed, if the merge failed due to conflicts.

This hook can be used in conjunction with a corresponding pre-commit hook to save and restore any form of metadata associated with the working tree (e.g.: permissions/ownership, ACLS, etc). See contrib/hooks/setgitperms.perl for an example of how to do this.

This hook is invoked by [git-merge](https://git-scm.com/docs/git-merge), which happens when a `git pull` is done on a local repository. The hook takes a single parameter, a status flag specifying whether or not the merge being done was a squash merge. This hook cannot affect the outcome of `git merge` and is not executed, if the merge failed due to conflicts.

This hook can be used in conjunction with a corresponding pre-commit hook to save and restore any form of metadata associated with the working tree (e.g.: permissions/ownership, ACLS, etc). See contrib/hooks/setgitperms.perl for an example of how to do this.

This hook is called by git-push and can be used to prevent a push from taking place. The hook is called with two parameters which provide the name and location of the destination remote, if a named remote is not being used both values will be the same.

Information about what is to be pushed is provided on the hook's standard input with lines of the form:

<local ref> SP <local sha1> SP <remote ref> SP <remote sha1> LF
For instance, if the command git push origin master:foreign were run the hook would receive a line like the following:

refs/heads/master 67890 refs/heads/foreign 12345
although the full, 40-character SHA-1s would be supplied. If the foreign ref does not yet exist the <remote SHA-1> will be 40 0. If a ref is to be deleted, the <local ref> will be supplied as (delete) and the <local SHA-1> will be 40 0. If the local commit was specified by something other than a name which could be expanded (such as HEAD~, or a SHA-1) it will be supplied as it was originally given.

If this hook exits with a non-zero status, git push will abort without pushing anything. Information about why the push is rejected may be sent to the user by writing to standard error.

This hook is called by [git-push](https://git-scm.com/docs/git-push) and can be used to prevent a push from taking place. The hook is called with two parameters which provide the name and location of the destination remote, if a named remote is not being used both values will be the same.

Information about what is to be pushed is provided on the hook's standard input with lines of the form:
```
<local ref> SP <local sha1> SP <remote ref> SP <remote sha1> LF
```
For instance, if the command `git push origin master:foreign` were run the hook would receive a line like the following:
```
refs/heads/master 67890 refs/heads/foreign 12345
```
although the full, 40-character SHA-1s would be supplied. If the foreign ref does not yet exist the `<remote SHA-1>` will be 40 `0`. If a ref is to be deleted, the `<local ref>` will be supplied as `(delete)` and the `<local SHA-1>` will be 40 `0`. If the local commit was specified by something other than a name which could be expanded (such as `HEAD~`, or a SHA-1) it will be supplied as it was originally given.

If this hook exits with a non-zero status, `git push` will abort without pushing anything. Information about why the push is rejected may be sent to the user by writing to standard error.

This hook is invoked by git-receive-pack when it reacts to git push and updates reference(s) in its repository. It executes on the remote repository once after all the refs have been updated.

It takes a variable number of parameters, each of which is the name of ref that was actually updated.

This hook is meant primarily for notification, and cannot affect the outcome of git receive-pack.

The post-update hook can tell what are the heads that were pushed, but it does not know what their original and updated values are, so it is a poor place to do log old..new. The post-receive hook does get both original and updated values of the refs. You might consider it instead if you need them.

When enabled, the default post-update hook runs git update-server-info to keep the information used by dumb transports (e.g., HTTP) up to date. If you are publishing a Git repository that is accessible via HTTP, you should probably enable this hook.

Both standard output and standard error output are forwarded to git send-pack on the other end, so you can simply echo messages for the user.

This hook is invoked by [git-receive-pack](https://git-scm.com/docs/git-receive-pack) when it reacts to `git push` and updates reference(s) in its repository. It executes on the remote repository once after all the refs have been updated.

It takes a variable number of parameters, each of which is the name of ref that was actually updated.

This hook is meant primarily for notification, and cannot affect the outcome of `git receive-pack`.

The **post-update** hook can tell what are the heads that were pushed, but it does not know what their original and updated values are, so it is a poor place to do log old..new. The **post-receive** hook does get both original and updated values of the refs. You might consider it instead if you need them.

When enabled, the default **post-update** hook runs `git update-server-info` to keep the information used by dumb transports (e.g., HTTP) up to date. If you are publishing a Git repository that is accessible via HTTP, you should probably enable this hook.

Both standard output and standard error output are forwarded to `git send-pack` on the other end, so you can simply `echo` messages for the user.

This hook is invoked by git-receive-pack when it reacts to git push and updates reference(s) in its repository, and when the push tries to update the branch that is currently checked out and the receive.denyCurrentBranch configuration variable is set to updateInstead. Such a push by default is refused if the working tree and the index of the remote repository has any difference from the currently checked out commit; when both the working tree and the index match the current commit, they are updated to match the newly pushed tip of the branch. This hook is to be used to override the default behaviour.

The hook receives the commit with which the tip of the current branch is going to be updated. It can exit with a non-zero status to refuse the push (when it does so, it must not modify the index or the working tree). Or it can make any necessary changes to the working tree and to the index to bring them to the desired state when the tip of the current branch is updated to the new commit, and exit with a zero status.

For example, the hook can simply run git read-tree -u -m HEAD "$1" in order to emulate git fetch that is run in the reverse direction with git push, as the two-tree form of git read-tree -u -m is essentially the same as git switch or git checkout that switches branches while keeping the local changes in the working tree that do not interfere with the difference between the branches.

This hook is invoked by [git-receive-pack](https://git-scm.com/docs/git-receive-pack) when it reacts to `git push` and updates reference(s) in its repository, and when the push tries to update the branch that is currently checked out and the `receive.denyCurrentBranch` configuration variable is set to `updateInstead`. Such a push by default is refused if the working tree and the index of the remote repository has any difference from the currently checked out commit; when both the working tree and the index match the current commit, they are updated to match the newly pushed tip of the branch. This hook is to be used to override the default behaviour.

The hook receives the commit with which the tip of the current branch is going to be updated. It can exit with a non-zero status to refuse the push (when it does so, it must not modify the index or the working tree). Or it can make any necessary changes to the working tree and to the index to bring them to the desired state when the tip of the current branch is updated to the new commit, and exit with a zero status.

For example, the hook can simply run `git read-tree -u -m HEAD "$1"` in order to emulate `git fetch` that is run in the reverse direction with `git push`, as the two-tree form of `git read-tree -u -m` is essentially the same as `git switch` or `git checkout` that switches branches while keeping the local changes in the working tree that do not interfere with the difference between the branches.

This hook is invoked by git gc --auto (see git-gc). It takes no parameter, and exiting with non-zero status from this script causes the git gc --auto to abort.

This hook is invoked by `git gc --auto` (see [git-gc](https://git-scm.com/docs/git-gc)). It takes no parameter, and exiting with non-zero status from this script causes the `git gc --auto` to abort.

This hook is invoked by commands that rewrite commits (git-commit when called with --amend and git-rebase; however, full-history (re)writing tools like git-fast-import or git-filter-repo typically do not call it!). Its first argument denotes the command it was invoked by: currently one of amend or rebase. Further command-dependent arguments may be passed in the future.

The hook receives a list of the rewritten commits on stdin, in the format

<old-sha1> SP <new-sha1> [ SP <extra-info> ] LF
The extra-info is again command-dependent. If it is empty, the preceding SP is also omitted. Currently, no commands pass any extra-info.

The hook always runs after the automatic note copying (see "notes.rewrite.<command>" in git-config) has happened, and thus has access to these notes.

The following command-specific comments apply:

rebase
For the squash and fixup operation, all commits that were squashed are listed as being rewritten to the squashed commit. This means that there will be several lines sharing the same new-sha1.

The commits are guaranteed to be listed in the order that they were processed by rebase.

This hook is invoked by commands that rewrite commits ([git-commit](https://git-scm.com/docs/git-commit) when called with `--amend` and [git-rebase](https://git-scm.com/docs/git-rebase); however, full-history (re)writing tools like [git-fast-import](https://git-scm.com/docs/git-fast-import) or [git-filter-repo](https://github.com/newren/git-filter-repo) typically do not call it!). Its first argument denotes the command it was invoked by: currently one of `amend` or `rebase`. Further command-dependent arguments may be passed in the future.

The hook receives a list of the rewritten commits on stdin, in the format
```
<old-sha1> SP <new-sha1> [ SP <extra-info> ] LF
```
The **extra-info** is again command-dependent. If it is empty, the preceding SP is also omitted. Currently, no commands pass any **extra-info**.

The hook always runs after the automatic note copying (see "notes.rewrite.\<command\>" in [git-config](https://git-scm.com/docs/git-config)) has happened, and thus has access to these notes.

The following command-specific comments apply:

**rebase**
For the **squash** and **fixup** operation, all commits that were squashed are listed as being rewritten to the squashed commit. This means that there will be several lines sharing the same **new-sha1**.
The commits are guaranteed to be listed in the order that they were processed by rebase.

This hook is invoked by git-send-email. It takes a single parameter, the name of the file that holds the e-mail to be sent. Exiting with a non-zero status causes git send-email to abort before sending any e-mails.

This hook is invoked by [git-send-email](https://git-scm.com/docs/git-send-email). It takes a single parameter, the name of the file that holds the e-mail to be sent. Exiting with a non-zero status causes `git send-email` to abort before sending any e-mails.

This hook is invoked when the configuration option core.fsmonitor is set to .git/hooks/fsmonitor-watchman. It takes two arguments, a version (currently 1) and the time in elapsed nanoseconds since midnight, January 1, 1970.

The hook should output to stdout the list of all files in the working directory that may have changed since the requested time. The logic should be inclusive so that it does not miss any potential changes. The paths should be relative to the root of the working directory and be separated by a single NUL.

It is OK to include files which have not actually changed. All changes including newly-created and deleted files should be included. When files are renamed, both the old and the new name should be included.

Git will limit what files it checks for changes as well as which directories are checked for untracked files based on the path names given.

An optimized way to tell git "all files have changed" is to return the filename /.

The exit status determines whether git will use the data from the hook to limit its search. On error, it will fall back to verifying all files and folders.

This hook is invoked when the configuration option core.fsmonitor is set to .git/hooks/fsmonitor-watchman or .git/hooks/fsmonitor-watchmanv2 depending on the version of the hook to use.

Version 1 takes two arguments, a version (1) and the time in elapsed nanoseconds since midnight, January 1, 1970.

Version 2 takes two arguments, a version (2) and a token that is used for identifying changes since the token. For watchman this would be a clock id. This version must output to stdout the new token followed by a NUL before the list of files.

The hook should output to stdout the list of all files in the working directory that may have changed since the requested time. The logic should be inclusive so that it does not miss any potential changes. The paths should be relative to the root of the working directory and be separated by a single NUL.

It is OK to include files which have not actually changed. All changes including newly-created and deleted files should be included. When files are renamed, both the old and the new name should be included.

Git will limit what files it checks for changes as well as which directories are checked for untracked files based on the path names given.

An optimized way to tell git "all files have changed" is to return the filename /.

The exit status determines whether git will use the data from the hook to limit its search. On error, it will fall back to verifying all files and folders.

This hook is invoked when the configuration option `core.fsmonitor` is set to `.git/hooks/fsmonitor-watchman`. It takes two arguments, a version (currently 1) and the time in elapsed nanoseconds since midnight, January 1, 1970.

The hook should output to stdout the list of all files in the working directory that may have changed since the requested time. The logic should be inclusive so that it does not miss any potential changes. The paths should be relative to the root of the working directory and be separated by a single NUL.

It is OK to include files which have not actually changed. All changes including newly-created and deleted files should be included. When files are renamed, both the old and the new name should be included.

Git will limit what files it checks for changes as well as which directories are checked for untracked files based on the path names given.

An optimized way to tell git "all files have changed" is to return the filename `/`.

The exit status determines whether git will use the data from the hook to limit its search. On error, it will fall back to verifying all files and folders.

This hook is invoked by git-p4 submit. It takes no parameters and nothing from standard input. Exiting with non-zero status from this script prevent git-p4 submit from launching. Run git-p4 submit --help for details.

This hook is invoked by `git-p4 submit`. It takes no parameters and nothing from standard input. Exiting with non-zero status from this script prevent `git-p4 submit` from launching. Run `git-p4 submit --help` for details.

Husky configuration.

Provide a JSON object that satisfies the schema "Husky configuration.". Here are the required top‑level fields: hooks. Return only the valid JSON object.


[System]
You are a helpful assistant that answers strictly in JSON. Here's the JSON schema you must adhere to:
<schema>
{"$schema":"http://json-schema.org/draft-04/schema#","additionalProperties":false,"definitions":{"duration":{"oneOf":[{"type":"integer"},{"type":"string","pattern":"^[0-9]+\\s*[years|yrs|y|weeks|wks|w|days|d|hours|hrs|h|minutes|mins|m!seconds|secs|s|milliseconds|ms]*$"}]},"loggerLevel":{"type":"string","enum":["all","trace","debug","info","warn","error","fatal","off"],"default":"off"},"transportProtocols":{"type":"string","enum":["http","https"]},"namespace":{"description":"Forces a specific namespace for connectors that perform namespace auto-detection (Advanced).","type":"string"},"outputDirectory":{"type":"string","default":"logs"},"sequential":{"type":"boolean","default":false},"hardwareProblemTemplate":{"type":"string","default":"Hardware problem on \\${FQDN\\} with \\${MONITOR_NAME\\}.\\${NEWLINE\\}\\${NEWLINE\\}\\${ALERT_DETAILS\\}\\${NEWLINE\\}\\${NEWLINE\\}\\${FULLREPORT\\}"},"hostType":{"type":"string","anyOf":[{"pattern":"^lin|^lnx$|^win|^ms.*win|^microsoft.*w|^oob$|^out|^vmware|^mgmt|^management|^esx|^blade|^net|^switch|^sto|^san|vms|tru64|osf|hp.*ux|aix|rs6000|^sun|^ora|sol"},{"enum":["win","linux","network","oob","storage","aix","hpux","solaris","tru64","vmx"]}]},"keyValuePairVariables":{"type":"object","propertyNames":{"pattern":"^[A-Za-z0-9_.-]+$"},"patternProperties":{".*":{"type":["number","string","boolean"]}}}},"id":"https://json.schemastore.org/hws-config.json","properties":{"collectPeriod":{"$ref":"#/definitions/duration","description":"Sets the collect period that Hardware Sentry uses to collects metrics from the monitored hosts (Default: 2m).","default":"2m"},"disableAlerts":{"description":"Disables Hardware Sentry's alerts for all the monitored hosts (Default: false).","type":"boolean","default":false},"discoveryCycle":{"description":"Sets the cycle that Hardware Sentry uses to perform discoveries and detect new components in your monitored environment. By default, Hardware Sentry runs a discovery after 30 collects.","type":"integer","default":"30"},"exporter":{"description":"Sets Hardware Sentry's internal Exporter configuration.","type":"object","properties":{"otlp":{"description":"Overrides Hardware Sentry's internal OTLP Exporter configuration.","type":["object","null"],"properties":{"headers":{"description":"Sets Hardware Sentry's OTLP Exporter headers, such as the `Authorization` header used to authenticate the Exporter with the OTLP gRPC Receiver.","type":"object"},"trustedCertificatesFile":{"description":"Sets Hardware Sentry's OTLP Exporter trusted certificates file (Default: security/otel.crt).","type":"string","default":"security/otel.crt"},"endpoint":{"description":"Configures the OTLP Receiver endpoint (Default: https://localhost:4317).","type":"string","default":"https://localhost:4317"}}}}},"extraLabels":{"$ref":"#/definitions/keyValuePairVariables","description":"Adds or overrides the attributes for all the monitored hosts. It is recommended to specify a different `site` label value for each OpenTelemetry Collector running the Hardware Sentry Agent."},"extraMetrics":{"description":"Adds additional static metrics to be exposed by Hardware Sentry.","type":"object","propertyNames":{"pattern":"^[A-Za-z0-9_.-]+$"},"patternProperties":{".*":{"type":"number"}}},"hardwareProblemTemplate":{"$ref":"#/definitions/hardwareProblemTemplate","description":"Overrides the default hardware problem template used to build the alert body for all the monitored hosts."},"hosts":{"description":"Configures the hosts to monitor.","type":"array","items":{"type":"object","properties":{"collectPeriod":{"$ref":"#/definitions/duration","description":"Sets the default collect period that Hardware Sentry uses to collects metrics from the monitored host (Default: 2m).","default":"2m"},"disableAlerts":{"description":"Disables Hardware Sentry's alerts for the monitored host (Default: false).","type":"boolean","default":false},"discoveryCycle":{"description":"Sets the cycle that Hardware Sentry uses to perform discoveries and detect new components for the specific host. By default, Hardware Sentry runs a discovery after 30 collects.","type":"integer","default":"30"},"excludedConnectors":{"description":"Sets the Connector(s) that must be excluded from the automatic detection.","type":"array","items":{"type":"string"}},"extraLabels":{"$ref":"#/definitions/keyValuePairVariables","description":"Adds or overrides the attributes of the monitored host."},"hardwareProblemTemplate":{"$ref":"#/definitions/hardwareProblemTemplate","description":"Overrides the default hardware problem template used to build the alert body for the monitored host."},"host":{"description":"Configures a new host to be monitored.","type":"object","properties":{"hostname":{"description":"Configures the hostname of the host to be monitored.","type":"string"},"id":{"description":"Configures the identifier of the host to be monitored (Optional). By default, the host identifier is the hostname property value.","type":"string"},"type":{"$ref":"#/definitions/hostType","description":"Configures the type of the host to be monitored."}},"required":["hostname","type"]},"hostGroup":{"description":"Configures several hosts which share the same characteristics.","type":"object","properties":{"hostnames":{"description":"Configures the hostnames of the hosts to be monitored.","oneOf":[{"type":"array","items":{"type":"string"}},{"type":"object","patternProperties":{"^[A-Za-z0-9.\\-_:]+$":{"type":"object","description":"Configures the hostname of the host to be monitored.","properties":{"extraLabels":{"$ref":"#/definitions/keyValuePairVariables","description":"Adds or overrides the attributes of the monitored host."}}}}}]},"type":{"$ref":"#/definitions/hostType","description":"Configures the type of the hosts to be monitored."}},"required":["hostnames","type"]},"http":{"description":"Configures the HTTP protocol to access the host.","type":"object","properties":{"https":{"description":"Enables HTTPS to access the host (Default: true).","type":"boolean","default":true},"password":{"description":"Sets the password used to establish the connection with the host through the HTTP protocol.","type":"string"},"port":{"description":"Sets the HTTPS port number used to perform HTTP requests (Default: 443).","type":"integer","default":443},"timeout":{"$ref":"#/definitions/duration","description":"Sets how long until the HTTP request times out (Default: 120s).","default":"120s"},"username":{"description":"Sets the username used to establish the connection with the host through the HTTP protocol.","type":"string"}}},"ipmi":{"description":"Configures the IPMI protocol to access the host.","type":"object","properties":{"password":{"description":"Sets the password used to establish the connection with the host through the IPMI protocol.","type":"string"},"timeout":{"$ref":"#/definitions/duration","description":"Sets how long until the IPMI request times out (Default: 120s).","default":"120s"},"username":{"description":"Sets the username used to establish the connection with the host through the IPMI protocol.","type":"string"}}},"loggerLevel":{"$ref":"#/definitions/loggerLevel","description":"Enables the debug mode of the core engine on the specific host (Default: off)."},"operationTimeout":{"description":"Sets how long until the engine's discovery and collect operations time out.","type":"integer"},"osCommand":{"description":"Configures the OS Command protocol to access the host.","type":"object","properties":{"sudoCommand":{"description":"Sets the sudo command to be used for the host to be monitored (Default: sudo).","type":"string","default":"sudo"},"timeout":{"$ref":"#/definitions/duration","description":"Sets how long until the local OS Command times out (Default: 120s).","default":"120s"},"useSudo":{"description":"Sets if sudo needs to be used for the local OS Command (Default: false).","type":"boolean","default":false},"useSudoCommands":{"description":"Sets the list of commands for which sudo is required.","type":"array","items":{"type":"string"}}}},"outputDirectory":{"$ref":"#/definitions/outputDirectory","description":"Sets the debug output directory for the monitored host. By default, the debug output file is saved in the `logs` directory under the Hardware Sentry's home directory."},"selectedConnectors":{"description":"Sets the Connector(s) to use to monitor the host. No automatic detection will be performed.","type":"array","items":{"type":"string"}},"sequential":{"$ref":"#/definitions/sequential","description":"Forces all the network calls to be executed in sequential order for the monitored host - NOT RECOMMENDED (Default: false)."},"snmp":{"description":"Configures the SNMP protocol to access the host.","type":"object","properties":{"community":{"description":"Sets the SNMP Community string to use to perform SNMP v1 queries (Default: public).","type":"string","default":"public"},"password":{"description":"SNMP v3 only - Sets the password to use for performing the SNMP query.","type":"string"},"port":{"description":"Sets the SNMP port number used to perform SNMP queries (Default: 161).","type":"integer","default":161},"privacy":{"description":"SNMP v3 only - Sets the type of encryption protocol.","type":"string","enum":["none","aes","des"]},"privacyPassword":{"description":"SNMP v3 only - Sets the password associated to the privacy protocol.","type":"string"},"timeout":{"$ref":"#/definitions/duration","description":"Sets how long until the SNMP request times out (Default: 120s).","default":"120s"},"username":{"description":"SNMP v3 only - Sets the username to use for performing the SNMP query.","type":"string"},"version":{"description":"Sets the version of the SNMP protocol (Default: v1).","type":"string","enum":["v1","v2c","v3-no-auth","v3-md5","v3-sha"],"default":"v1"}}},"ssh":{"description":"Configures the SSH protocol to access the host.","type":"object","properties":{"password":{"description":"Sets the password to use for performing the SSH query.","type":"string"},"privateKey":{"description":"Sets the private Key File to use to establish the connection to the host through the SSH protocol.","type":"string"},"sudoCommand":{"description":"Sets the sudo command to be used.","type":"string","default":"sudo"},"timeout":{"$ref":"#/definitions/duration","description":"Sets how long until the command times out (Default: 120s).","default":"120s"},"useSudo":{"description":"Sets if sudo needs to be used for the SSH Command (Default: false).","type":"boolean","default":false},"useSudoCommands":{"description":"Sets the list of commands for which sudo is required.","type":"array","items":{"type":"string"}},"username":{"description":"Sets the username to use for performing the SSH query.","type":"string"}}},"wbem":{"description":"Configures the WBEM protocol to access the host.","type":"object","properties":{"namespace":{"$ref":"#/definitions/namespace"},"password":{"description":"Sets the password used to establish the connection with the host through the WBEM protocol.","type":"string"},"port":{"description":"Sets the HTTPS port number used to perform WBEM queries (Default: 5989 for HTTPS or 5988 for HTTP).","type":"integer","default":5989},"protocol":{"$ref":"#/definitions/transportProtocols","description":"Sets the protocol used to access the host (Default: https).","default":"https"},"timeout":{"$ref":"#/definitions/duration","description":"Sets how long until the WBEM request times out (Default: 120s).","default":"120s"},"username":{"description":"Sets the username used to establish the connection with the host through the WBEM protocol.","type":"string"}}},"winrm":{"description":"Configures the WinRM protocol to access the host.","type":"object","properties":{"authentications":{"description":"Sets an ordered list of authentication schemes (Default: [\"ntlm\"]).","type":"array","items":{"type":"string","enum":["ntlm","kerberos"]},"default":["ntlm"]},"namespace":{"$ref":"#/definitions/namespace"},"password":{"description":"Sets the password used to establish the connection with the host through the WinRM protocol.","type":"string"},"port":{"description":"Sets the port number used to perform WQL queries and commands (Default: 5985 for HTTP or 5986 for HTTPS).","type":"integer"},"protocol":{"$ref":"#/definitions/transportProtocols","description":"Sets the protocol used to access the host (Default: http).","default":"http"},"timeout":{"$ref":"#/definitions/duration","description":"Sets how long until the WinRM request times out (Default: 120s).","default":"120s"},"username":{"description":"Sets the username used to establish the connection with the host through the WinRM protocol.","type":"string"}}},"wmi":{"description":"Configures the WMI protocol to access the host.","type":"object","properties":{"namespace":{"$ref":"#/definitions/namespace"},"password":{"description":"Sets the password used to establish the connection with the host through the WMI protocol.","type":"string"},"timeout":{"$ref":"#/definitions/duration","description":"Sets how long until the WMI request times out (Default: 120s).","default":"120s"},"username":{"description":"Sets the username used to establish the connection with the host through the WMI protocol.","type":"string"}}}},"oneOf":[{"required":["host"]},{"required":["hostGroup"]}]}},"jobPoolSize":{"description":"Sets the number of jobs that Hardware Sentry can run simultaneously (Default: 20).","type":"integer","default":"20"},"loggerLevel":{"$ref":"#/definitions/loggerLevel","description":"Enables the debug mode of the core engine (Default: off)."},"otelCollector":{"description":"Customizes the OpenTelemetry Collector sub-process.","type":"object","properties":{"commandLine":{"description":"Overrides the OpenTelemetry Collector command line.","type":"array","items":{"type":"string"}},"environment":{"$ref":"#/definitions/keyValuePairVariables","description":"Configures the OpenTelemetry Collector environment variables."},"output":{"description":"Configures where to print the OpenTelemetry Collector's output (Default: log).","type":"string","enum":["log","console","silent"],"default":"log"},"workingDir":{"description":"Configures the working directory of the OpenTelemetry Collector.","type":"string"},"disabled":{"description":"Disables the OpenTelemetry Collector (Default: false).","type":"boolean","default":false}}},"outputDirectory":{"$ref":"#/definitions/outputDirectory","description":"Sets the debug output directory for all the monitored hosts. By default, the debug output files are saved in the `logs` directory under the Hardware Sentry's home directory."},"resolveHostnameToFqdn":{"description":"Displays the configured hostname in the Host Resource `host.name` attribute instead of the resolved FQDN (Default: false).","type":"boolean","default":false},"sequential":{"$ref":"#/definitions/sequential","description":"Forces all the network calls to be executed in sequential order for all the monitored hosts - NOT RECOMMENDED (Default: false)."}},"title":"Hardware Sentry configuration file","type":"object"}
</schema>

[User] Provide a JSON object that satisfies the schema "Hardware Sentry configuration file". Here are the required top‑level fields: none (all optional). Return only the valid JSON object.

all trace debug info warn error fatal off

Forces a specific namespace for connectors that perform namespace auto-detection (Advanced).

Hardware problem on \${FQDN\} with \${MONITOR_NAME\}.\${NEWLINE\}\${NEWLINE\}\${ALERT_DETAILS\}\${NEWLINE\}\${NEWLINE\}\${FULLREPORT\}

win linux network oob storage aix hpux solaris tru64 vmx

Sets the collect period that Hardware Sentry uses to collects metrics from the monitored hosts (Default: 2m).

Disables Hardware Sentry's alerts for all the monitored hosts (Default: false).

Sets the cycle that Hardware Sentry uses to perform discoveries and detect new components in your monitored environment. By default, Hardware Sentry runs a discovery after 30 collects.

Sets Hardware Sentry's internal Exporter configuration.

Overrides Hardware Sentry's internal OTLP Exporter configuration.

Sets Hardware Sentry's OTLP Exporter headers, such as the `Authorization` header used to authenticate the Exporter with the OTLP gRPC Receiver.

Sets Hardware Sentry's OTLP Exporter trusted certificates file (Default: security/otel.crt).

Configures the OTLP Receiver endpoint (Default: https://localhost:4317).

Adds or overrides the attributes for all the monitored hosts. It is recommended to specify a different `site` label value for each OpenTelemetry Collector running the Hardware Sentry Agent.

Adds additional static metrics to be exposed by Hardware Sentry.

Overrides the default hardware problem template used to build the alert body for all the monitored hosts.

Configures the hosts to monitor.

Sets the default collect period that Hardware Sentry uses to collects metrics from the monitored host (Default: 2m).

Disables Hardware Sentry's alerts for the monitored host (Default: false).

Sets the cycle that Hardware Sentry uses to perform discoveries and detect new components for the specific host. By default, Hardware Sentry runs a discovery after 30 collects.

Sets the Connector(s) that must be excluded from the automatic detection.

Adds or overrides the attributes of the monitored host.

Overrides the default hardware problem template used to build the alert body for the monitored host.

Configures a new host to be monitored.

Configures the hostname of the host to be monitored.

Configures the identifier of the host to be monitored (Optional). By default, the host identifier is the hostname property value.

Configures the type of the host to be monitored.

Configures several hosts which share the same characteristics.

Configures the hostnames of the hosts to be monitored.

Configures the type of the hosts to be monitored.

Configures the HTTP protocol to access the host.

Enables HTTPS to access the host (Default: true).

Sets the password used to establish the connection with the host through the HTTP protocol.

Sets the HTTPS port number used to perform HTTP requests (Default: 443).

Sets how long until the HTTP request times out (Default: 120s).

Sets the username used to establish the connection with the host through the HTTP protocol.

Configures the IPMI protocol to access the host.

Sets the password used to establish the connection with the host through the IPMI protocol.

Sets how long until the IPMI request times out (Default: 120s).

Sets the username used to establish the connection with the host through the IPMI protocol.

Enables the debug mode of the core engine on the specific host (Default: off).

Sets how long until the engine's discovery and collect operations time out.

Configures the OS Command protocol to access the host.

Sets the sudo command to be used for the host to be monitored (Default: sudo).

Sets how long until the local OS Command times out (Default: 120s).

Sets if sudo needs to be used for the local OS Command (Default: false).

Sets the list of commands for which sudo is required.

Sets the debug output directory for the monitored host. By default, the debug output file is saved in the `logs` directory under the Hardware Sentry's home directory.

Sets the Connector(s) to use to monitor the host. No automatic detection will be performed.

Forces all the network calls to be executed in sequential order for the monitored host - NOT RECOMMENDED (Default: false).

Configures the SNMP protocol to access the host.

Sets the SNMP Community string to use to perform SNMP v1 queries (Default: public).

SNMP v3 only - Sets the password to use for performing the SNMP query.

Sets the SNMP port number used to perform SNMP queries (Default: 161).

SNMP v3 only - Sets the type of encryption protocol.

SNMP v3 only - Sets the password associated to the privacy protocol.

Sets how long until the SNMP request times out (Default: 120s).

SNMP v3 only - Sets the username to use for performing the SNMP query.

Sets the version of the SNMP protocol (Default: v1).

Configures the SSH protocol to access the host.

Sets the password to use for performing the SSH query.

Sets the private Key File to use to establish the connection to the host through the SSH protocol.

Sets the sudo command to be used.

Sets how long until the command times out (Default: 120s).

Sets if sudo needs to be used for the SSH Command (Default: false).

Sets the list of commands for which sudo is required.

Sets the username to use for performing the SSH query.

Configures the WBEM protocol to access the host.

Sets the password used to establish the connection with the host through the WBEM protocol.

Sets the HTTPS port number used to perform WBEM queries (Default: 5989 for HTTPS or 5988 for HTTP).

Sets the protocol used to access the host (Default: https).

Sets how long until the WBEM request times out (Default: 120s).

Sets the username used to establish the connection with the host through the WBEM protocol.

Configures the WinRM protocol to access the host.

Sets an ordered list of authentication schemes (Default: ["ntlm"]).

Sets the password used to establish the connection with the host through the WinRM protocol.

Sets the port number used to perform WQL queries and commands (Default: 5985 for HTTP or 5986 for HTTPS).

Sets the protocol used to access the host (Default: http).

Sets how long until the WinRM request times out (Default: 120s).

Sets the username used to establish the connection with the host through the WinRM protocol.

Configures the WMI protocol to access the host.

Sets the password used to establish the connection with the host through the WMI protocol.

Sets how long until the WMI request times out (Default: 120s).

Sets the username used to establish the connection with the host through the WMI protocol.

Sets the number of jobs that Hardware Sentry can run simultaneously (Default: 20).

Enables the debug mode of the core engine (Default: off).

Customizes the OpenTelemetry Collector sub-process.

Overrides the OpenTelemetry Collector command line.

Configures the OpenTelemetry Collector environment variables.

Configures where to print the OpenTelemetry Collector's output (Default: log).

Configures the working directory of the OpenTelemetry Collector.

Disables the OpenTelemetry Collector (Default: false).

Sets the debug output directory for all the monitored hosts. By default, the debug output files are saved in the `logs` directory under the Hardware Sentry's home directory.

Displays the configured hostname in the Host Resource `host.name` attribute instead of the resolved FQDN (Default: false).

Forces all the network calls to be executed in sequential order for all the monitored hosts - NOT RECOMMENDED (Default: false).

Hardware Sentry configuration file

Provide a JSON object that satisfies the schema "Hardware Sentry configuration file". Here are the required top‑level fields: none (all optional). Return only the valid JSON object.