description: [Deprecated] Options that are passed to the compiler. Use 'buildOptions' instead.

enum: portable full none

description: Options that are passed to the compiler.

description: Set this option to preserve reference assemblies and other context data to allow for runtime compilation.

default: csc

description: Defines glob patterns and file path to include for compilation.

type: string array object

type: string array

description: List of file globbing patterns to be included.

description: List of file globbing patterns to be excluded.

description: List of file paths to be included.

description: List of file paths to be excluded.

description: Pairs of destination folders and glob patterns specifying additional files to include/exclude.

description: Defines glob patterns and file paths of resource files to include for compilation.

description: Defines glob patterns and file paths to include for copying to build output.

description: Enables/disables server garbage collection.

description: Enables/disables concurrent garbage collection.

description: Limits the number of heaps created by the garbage collector.

description: Specifies the exact processors that garbage collector threads should use.

description: Specifies the list of processors to use for garbage collector threads.

description: Specifies whether to affinitize garbage collection threads with processors. To affinitize a GC thread means that it can only run on its specific CPU. A heap is created for each GC thread.

description: Specifies the maximum commit size, in bytes, for the GC heap and GC bookkeeping.

description: Specifies the GC heap usage as a percentage of the total memory.

description: Configures whether segments that should be deleted are put on a standby list for future use or are released back to the operating system (OS).

description: Specifies the threshold size, in bytes, that causes objects to go on the large object heap (LOH).

description: Sets the minimum number of threads for the thread pool.

description: Sets the maximum number of threads for the thread pool.

description: Defines options pertaining to the packaging of the project output into a NuGet package.

description: A short description of the package.

description: List of owners of the package.

description: A link to the license for the package.

default: git

description: Defines glob patterns and file paths to include in the generated NuGet package.

description: Defines glob patterns and file paths to include in publish output.

$ref: #/definitions/dependencies

$ref: #/definitions/compilationOptions

$ref: #/definitions/buildOptions

description: Allow packages supporting these frameworks to be installed in this target, regardless of the compatibility rules.

enum: all runtime compile build contentFiles native analyzers none

$ref: #/definitions/libraryIncludeFlag

description: Restrict this dependency to matching only a Project or a Package.

description: Each dependency is defined by a name and a version. Dependencies are resolved from NuGet feeds defined by your package sources and projects located in the directories specified by the 'global.json' file.

description:
A command line script or scripts.

Available variables:
%project:Directory% - The project directory
%project:Name% - The project name
%project:Version% - The project version

description: The author of the application.

description: [Deprecated] Pairs of destination folders and glob patterns specifying additional files to include in the output NuGet package. (data type: JSON map). Example: { "tools/": "tools/**/*.*" }. Use 'files' in 'packOptions' instead.

description: [Deprecated] Glob pattern to specify files to exclude from publish output. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]. Use 'publishOptions' instead.

description: [Deprecated] Glob pattern to specify files to compile. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]. Use 'compile' in 'buildOptions' instead.

description: [Deprecated] Glob pattern to specify files to exclude from compilation. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]. Use 'compile' in 'buildOptions' instead.

description: [Deprecated] Files to include in compilation (overrides 'compileExclude'). (data type: string or array). Example: [ "Folder1/File1.ext", "Folder2/File2.ext" ]. Use 'compile' in 'buildOptions' instead.

description: [Deprecated] Glob pattern to specify files to include as content. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]. Use 'publishOptions' to publish or 'copyToOutput' in 'buildOptions' to copy to build output instead.

description: [Deprecated] Glob pattern to specify files to exclude from the content list. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]. Use 'publishOptions' to publish or 'copyToOutput' in 'buildOptions' to copy to build output instead.

description: [Deprecated] Files to include as content (overrides 'contentExclude'). (data type: string or array). Example: [ "Folder1/File1.ext", "Folder2/File2.ext" ]. Use 'publishOptions' to publish or 'copyToOutput' in 'buildOptions' to copy to build output instead.

description: Glob pattern to specify files to use for preprocessing. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]

description: Glob pattern to specify files to exclude from use for preprocessing. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]

description: Files to include to use for preprocessing (overrides 'preprocessExclude'). (data type: string or array). Example: [ "Folder1/File1.ext", "Folder2/File2.ext" ]

description: [Deprecated] Glob pattern to specify files to include as resources. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]. Use 'embed' in 'buildOptions' instead.

description: [Deprecated] Glob pattern to specify files to exclude from the resources list. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]. Use 'embed' in 'buildOptions' instead.

description: [Deprecated] Files to include as resources (overrides 'resourceExclude'). (data type: string or array). Example: [ "Folder1/File1.ext", "Folder2/File2.ext" ]. Use 'embed' in 'buildOptions' instead.

description: Glob pattern to specify files to share with dependent projects. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]

description: Glob pattern to specify files to exclude from sharing with dependent projects. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]

description: Files to include for sharing with dependent projects (overrides 'sharedExclude'). (data type: string or array). Example: [ "Folder1/File1.ext", "Folder2/File2.ext" ]

description: [Deprecated] Glob pattern to indicate files to exclude from other glob patterns, in addition to the default patterns specified in 'excludeBuiltIn'. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]. Use 'exclude' within 'compile' or 'embed' instead.

description: [Deprecated] Default glob pattern to indicate files to exclude from other glob patterns. (data type: string or array with glob pattern(s)). Example: [ "Folder1/*.ext", "Folder2/*.ext" ]. Use 'exclude' within 'compile' or 'embed' instead.

description: The name of the test runner to use with this project

description: Configurations are named groups of compilation settings. There are two defaults built into the runtime: 'Debug' and 'Release'.

description: Copyright details for the package.

description: [Deprecated] A URL for the image to use as the icon for the package. This should be a 32x32-pixel .png file that has a transparent background. Use this in 'packOptions' instead.

description: [Deprecated] A link to the license for the package. Use this in 'packOptions' instead.

description: [Deprecated] A Boolean value that specifies whether the client needs to ensure that the package license (described by licenseUrl) is accepted before the package is installed. Use this in 'packOptions' instead.

description: [Deprecated] List of owners of the package. Use this in 'packOptions' instead.

description: A URL for the home page of the package.

description: [Deprecated] A short description of the package. Use this in 'packOptions' instead.

description: [Deprecated] A space-delimited list of tags and keywords that describe the package. Use this in 'packOptions' instead.

description: The human-friendly title of the package

description: [Deprecated] A description of the changes made in each release of the package. Use this in 'packOptions' instead.

description: The locale ID for the package, such as en-us.

description: The description of the project/package.

description: Target frameworks that will be built, and dependencies that are specific to the build of this project for that framework.

description: Overrides the generated resource names with custom ones.

description: [Deprecated] Contains information about the repository where the project is stored. Use this in 'packOptions' instead.

description: Scripts to execute during the various stages.

description: The version of the project/package. Examples: 1.2.3, 1.2.3-beta, 1.2.3-*

description: Project-specific command line tools accessible when in the project.json directory.

description: List of runtime identifiers supported by this project (used when building standalone applications).

title: JSON schema for .NET Core project.json files


type: object

type: array

type: string

type: boolean

type: string object

default: default

enum: default build

description:
A command line script or scripts.

Available variables:
%project:Directory% - The project directory
%project:Name% - The project name
%project:Version% - The project version

description: List of files to exclude from publish output (dnu publish).

description: Glob pattern to specify additional code files that needs to be compiled. (data type: string or array with glob pattern(s)). Example: [ "folder1/**/*.cs", "folder2/**/*.cs" ]

description: Glob pattern to indicate code files that needs to be excluded from compilation. (data type: string or array with glob pattern(s)). Example: [ "folder1/**/*.cs", "folder2/**/*.cs" ]

description: Individual file paths relative to application root that needs to be included for compilation. (data type: string or array). Example: [ "folder1/test1.cs", "folder2/test2.cs" ]

description: Glob pattern to indicate the default code files that are included for compilation. (data type: string or array with glob pattern(s)). Example: [ "**/*.cs", "../folder2/**/*.cs" ]

description: Glob pattern to indicate the default files to be excluded from processing. (data type: string or array with glob pattern(s)).

description: Glob pattern to indicate all the additional files to be excluded from processing. (data type: string or array with glob pattern(s)).

description: Glob pattern to indicate all the code files to be pre-processed. (data type: string or array with glob pattern(s)).

description: Glob pattern to indicate all the code files to be excluded from pre-processing. (data type: string or array with glob pattern(s)).

description: Glob pattern to indicate specific code files to be included for pre-processing. (data type: string or array).

description: Glob pattern to indicate all the files that need to be compiled as resources. (data type: string or array with glob pattern(s))

description: Glob pattern to indicate files that need to be excluded from being compiled as resources. (data type: string or array with glob pattern(s))

description: Glob pattern to indicate individual files that need to be compiled as resources. (data type: string or array).

description: Glob pattern to specify the code files to share with dependent projects. Example: [ "folder1/*.cs", "folder2/*.cs" ]

description: Glob pattern to specify the code files to be excluded from sharing with dependent projects. Example: [ "folder1/*.cs", "folder2/*.cs" ]

description: Glob pattern to specify the individual code files to be shared with dependent projects. Example: [ "folder1/shared1.cs", "folder2/shared2.cs" ]

description: Glob pattern to specify the files to be considered as content on dnu publish. Example: [ "folder1/**/*" ]

description: Glob pattern to specify the files to be excluded from being content on dnu publish. Example: [ "folder1/*.cs", "folder2/*.cs" ]

description: Glob pattern to specify the individual files to be content files on dnu publish. Example: [ "folder1/content.cs", "folder2/content2.img" ]

description: Configurations are named groups of compilation settings. There are 2 defaults built into the runtime namely 'Debug' and 'Release'.

description: Copyright details for the package

description: The description of the application

$ref: #/definitions/configType

description: A URL for the image to use as the icon for the package. This should be a 32x32-pixel .png file that has a transparent background.

description: A link to the license that the package is under

description: A URL for the home page of the package

$ref: #/definitions/script

description: A short description of the package

description: The human-friendly title of the package

description: The version of the application. Example: 1.2.0.0

description: Specifying the webroot property in the project.json file specifies the web server root (aka public folder). In visual studio, this folder will be used to root IIS. Static files should be put in here.

description: Specify a unique id to manage the development time user secrets of the application

title: JSON schema for ASP.NET project.json files


title: Configuration for the edgeHub module

required: schemaVersion routes

type: integer

pattern: \$upstream

pattern: ^in$|^out$

$ref: #/definitions/policy

title: JSON schema for Azure IoT EdgeHub Deployment version 1.2


requirements.json

title: Name

title: Source

enum: galaxy url file git dir subdirs

title: Type

title: Version

title: CollectionModel

title: CollectionStringModel

title: Include

title: IncludeModel

$ref: #/$defs/CollectionModel

$ref: #/$defs/CollectionStringModel

title: Collections

$ref: #/$defs/RoleModel

title: Roles

title: Requirements v2

title: Name

title: Scm

title: Src

default: master

title: Version

title: Role

$ref: #/$defs/IncludeModel

title: Ansible Requirements Schema


pattern: ^(native|web|dotnet|hybrid)$

type: number

pattern: ^(test|debug|release)$

pattern: ^(llvm|gcc)$

pattern: ^(dotnet-cli|msbuild)$


$comment: JSON Schema for CRYENGINE 5.5

title: Variable name

description: CVar name

title: Command name

description: Console command name

$ref: #/definitions/cvars

title: Value of the CVar

description: The default value of the CVar

required: name value

title: Assets folder

description: This indicates where the assets are stored

default: Assets

title: Code folder

description: This indicates where the code is stored

default: Code

title: Lib's name

title: Lib's name to import for all the supported platforms

title: Lib's name to import for the win_x64 platform

title: Lib's name to import for the win_x86 platform

title: Project name

description: This indicates the project name

title: Project GUID

title: Engine version

description: This indicates which engine version will be used

title: Plugin name

description: Required plugin's name

examples: CryDefaultEntities CrySensorSystem CryPerceptionSystem CryUserAnalytics CryOSVR CryOculusVR CryOpenVR CryLobby

title: Plugin type

description: EPluginType::Native if it's a C++ plugin, EPluginType::Managed if it's a C# one

title: This plugin will be used only by these platforms

enum: pc ps4 xboxone linux

required: path type

title: Project version

$ref: #/definitions/commands

title: Value of the command

description: Arguments that has to be passed to the command. Leave empty if it has not parameters

required: content info require version

title: CryProj schema


huskyrc.json

x-intellij-language-injection: Shell Script

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

title: Skipping Git hooks installation.

title: Git hooks.

$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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

description:
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.

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.

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.

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.

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.

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.

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.

description:
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.

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.

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

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.

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.

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.

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`.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

title: Husky configuration.


ops.schema.json

title: ops.yaml

description: Confirguration for `ops`


apibuilder.json

title: API documentation

description: Specifies the version of the API Builder specification that this file is written for. The latest version can be found by visiting /apicollective/apibuilder-spec.

title: contact information

description: Specifies contact information for this service.

$ref: #/definitions/contact

description: Specifies the license under which this service is released.

$ref: #/definitions/license

title: contact information

description: Specifies contact information for this service

description: Identifying name of the contact person/organization

description: URL pointing to the contact information

description: Email address of the contact person/organization

title: license

description: specifies the license under which this service is released

description: Name of the license - e.g. MIT

description: URL of the license itself

title: import

description: The complete URI to the service specification that we are importing. Within API Builder, you can find the URL to the service specification by clicking on the "service.json" link for a service.

title: header

description: The name of the header.

description: The type of this header. Acceptable values are either the name of an enum or string. To specify a collection (meaning multiple values for this header can be provided), the type name can be wrapped with "[]". For example, to specify that the type is a collection of strings, use "[string]".

description: boolean: true|false. By default, all headers are considered required. To make a parameter optional, set "required" to false.

description: The default value for this header. If specified, generated clients will automatically include this header in all requests. Default values must be specified as strings.

description: Optional description for what this header provides. Supports GFM.

description: JSON Array defining additional meta data about this header for use by generators.

$ref: #/definitions/attribute

$ref: #/definitions/deprecation

required: name type

title: annotation

title: annotation

description: An annotation is just a short key that can be used to tag any field in any model of this API.

description: Describes what the annotation is used for.

title: attribute

description: the name and identifier of the attribute.

title: json object

description: a JSON object that is usually utilized by a downstream Generator.

title: json object

description: JSON Object that indicates that this object is deprecated.

description: Optional, but recommended to contain notes for what the user is supposed to do now that this property is deprecated. Supports GFM.

title: enumeration

title: name

description: The name of the enum. Names must be alphanumeric and must start with a letter. Valid characters are a-z, A-Z, 0-9 and _ characters. The name must be unique in the set of names assigned to enums, interfaces, models, or unions types.

description: Specifies the optional, plural form of the name. By default, we will pluralize the name using a basic set of english heuristics. The plural is used as a default in cases where it is more natural to specify web services. For example, the default path for a resource will be the plural.

description: Optional longer description for this enum.

description: JSON Array of EnumValue objects. Each element defines a valid value and an optional description.

$ref: #/definitions/enumvalues

description: JSON Array defining additional meta data about this enum for use by generators.

title: evaluates

description: The name of the value. Names must start with a letter.

description: The actual string representation of this value when serializing. If not specified, defaults to 'name'.

description: Optional description for what this enum value provides. Supports GFM.

description: JSON Array defining additional meta data about this enum value for use by generators.

title: interface

title: name

description: Name specifies the name of the interface. Names must be alphanumeric and start with a letter. Valid characters are a-z, A-Z, 0-9 and _ characters. The name must be unique in the set of names assigned to enums, interfaces, or models. Note you may define an interface and a union of the same name.

description: Optional description for what this model provides. Supports GFM.

description: JSON Array of 0 or more Fields.

$ref: #/definitions/field

description: JSON Array defining additional meta data about this model for use by generators.

title: field

description: Specifies the name of the field. Names must be alphanumeric and start with a letter. Valid characters are a-z, A-Z, 0-9 and _ characters.

description: Specifies the type of this field. Acceptable values include the name of either an enum, a model, or a (primitive type). To specify a List, the type name can be wrapped with "[]". For example, to specify that the type is a collection of strings, use "[string]". To specify a Map, the type name can be prefixed with "map[type]". For example, to specify that the type is a Map of string to long, use "map[long]". Note that for map, the keys must be strings (per the JSON specification).

description: Optional description for what this field provides. Supports GFM.

description: By default, all fields are considered required. To make a field optional, set "required" to false. When a field is marked as required, it must be present in any form of a model for that form to be valid. In client-server scenario, this means that any defaults that are present in the model must be applied by the client. If you want a default to be applied by the receiver, you should mark the field as "required": false

description: Optional default value. The value must be valid for the type specified for this field. For example, if you specify a field named 'limit' with type 'integer', an acceptable default would be 10.

description: Optional - an example value for this field used only in the produced documentation

description: Optional - For a string, refers to the minimum length. For an array, the minimum number of elements in the array. For example, a value of 1 for an array would indicate the array must have at least 1 element.

description: Optional - For a string, refers to the maximum length. For an array, the maximum number of elements in the array. For example, a value of 1 for an array would indicate the array must have at most 1 element.

description: JSON Array defining additional meta data about this field for use by generators.

description: JSON Array of type string where each value indicates the name of a declared annotation (optional),

title: model

description: specifies the name of the model. Names must be alphanumeric and start with a letter. Valid characters are a-z, A-Z, 0-9 and _ characters. The name must be unique in the set of names assigned to enums, interfaces, models, or unions types.

title: model

description: Description for what this model provides.

description: JSON Array of type string where each value indicates the name of a declared interface

title: union

description: Name specifies the name of the interface. Names must be alphanumeric and start with a letter. Valid characters are a-z, A-Z, 0-9 and _ characters. The name must be unique in the set of names assigned to enums, unions, or models. Note you may define an interface and a union of the same name, but in this case it is required to list that interface in the interfaces field.

description: Specifies an optional, but recommended, name for a type discriminator field which can then be used in serialization / deserialization to identify the type of object. For example, if not specified, a code generator may serialize the union type into a JSON structure of { "type" => object }. If a discriminator is provided, the same code generator can flatten the JSON representation to, for example: { "discriminator" => "xxx", "field1" => "yyy" }. If provided, the name of the discriminator field must be unique across all of the fields across all of the types of this union.

description: Optional description for what this union provides. Supports GFM.

description: Specifies the individual types that are part of this union type.

$ref: #/definitions/uniontype

description: JSON Array defining additional meta data about this union for use by generators.

title: union type

description:
Specifies the type to include in this union type. Acceptable values include the name of either an enum, a model, or a (primitive type).
description optional description for what this type provides. Supports GFM.

description: If true, indicates that this type should be used as the default when deserializing union types. This field is only used by union types that require a discriminator and sets the default value for that discriminator during deserialization.

description: The discriminator value defines the string to use in the discriminator field to identify this type. If not specified, the discriminator value will default to the name of the type itself.

description: JSON Array defining additional meta data about this union type for use by generators.

title: resource

title: name

description: The name of the model or enum that this resource represents

description: Optional path where this resource is located. If not provided, defaults to the plural of the typeName, with some assumptions of formatting for web (e.g. lower case, dash separated). Path parameters can be specified by prefixing a path element with ':'. For example, a path of '/:guid' would imply that all operations for this path will require a parameter named 'guid' of type 'string'

description: Optional description for what this resource provides. Supports GFM.

description: One or more operations is required.

description: JSON Array defining additional meta data about this resource for use by generators.

title: operation

description: The HTTP method for this operation

description: Optional path for this particular operation. If not provided, defaults to no additional path. Path parameters can be specified by prefixing a path element with ':'. For example, a path of '/:guid' would imply that this operation is available at /resource_path/:guid. Path parameter types are inferred by looking for a field with that name on the model associated with this resource. If not found, the datatype of any path parameter will be string.

description: Optional description for what this operation provides. Supports GFM.

description: Optional specification for the type of the body of this request. For all operations that support bodies (e.g. POST, PUT, PATCH), allows you to specify the type of the body.

description: Optional JSON Array of the parameters to this method. By default, for GET methods, parameters are assumed to be in the path or in the query. For other methods, parameters are assumed to be in the path or form body, unless you have explicitly specified a body in which case parameters can be provided in the path or the query.

description: Optional JSON Object of HTTP Response Code to Response. If not provided, an HTTP NoContent response is assumed. Only responses for HTTP status codes that are interesting should be documented.

description: JSON array defining additional meta data about this operation for use by generators.

title: parameter

description: The name of the parameter. Names must be alphanumeric and must start with a letter. Valid characters are a-z, A-Z, 0-9 and _ characters.

description: Specifies the type of this parameter. Acceptable values include the name of either an enum, a model, or a (primitive type). To specify a List, the type name can be wrapped with "[]". For example, to specify that the type is a collection of strings, use "[string]". To specify a Map, the type name can be prefixed with "map[type]". For example, to specify that the type is a Map of string to long, use "map[long]". Note that for map, the keys must be strings (per the JSON specification).

description: One of: path, query, form, header. Defines the location of this parameter. Default location varies based on the context of the parameter (e.g. if the operation method is a POST, the default will be Form; if a GET, the default will be Query)

description: Optional description for what this parameter provides. Supports GFM.

description: By default all parameters are considered required. To make a parameter optional, set "required" to false.

description: Optional default value. The value must be valid for the type specified for this parameter. For example, if you specify a parameter named 'limit' with type 'integer', an acceptable default would be 10

description: Optional - an example value for this parameter used only in the produced documentation

description: JSON array defining additional meta data about this parameter for use by generators.

title: response

title: HTTP status

description:
A valid HTTP status code for this response (e.g. 200). Only status codes that have interesting return types should be documented. You can also specify an HTTP status code of 'default' to map to all other non documented types. This is useful to capture a generic error type that would be returned for non documented response codes.

There are a few conventions enforced:
- HTTP Response codes of 5xx cannot be explicitly specified and are handled automatically to ensure consistent behavior in generated client libraries.
- HTTP Response codes of 204 and 304 indicate that no content is returned, so they must use a type of unit.

description: Specifies the type of this response. Acceptable values include the name of either an enum, a model, or a (primitive type). To specify a List, the type name can be wrapped with "[]". For example, to specify that the type is a collection of strings, use "[string]". To specify a Map, the type name can be prefixed with "map[type]". For example, to specify that the type is a Map of string to long, use "map[long]". Note that for map, the keys must be strings (per the JSON specification).

description: Optional description for what this response provides. Supports GFM.

description: JSON Array defining additional meta data about this service. Attributes are used to add custom extensions to API Builder and are typically used by generators to enable advanced code generation.

title: body

description: Specifies the type of this body. Acceptable values include the name of either an enum, a model, or a (primitive type). To specify a List, the type name can be wrapped with "[]". For example, to specify that the type is a collection of strings, use "[string]". To specify a Map, the type name can be prefixed with "map[type]". For example, to specify that the type is a Map of string to long, use "map[long]". Note that for map, the keys must be strings (per the JSON specification).

description: Optional description for what this body provides. Supports GFM.

description: JSON Array defining additional meta data about this body for use by generators.

description: JSON Schema for API Builder's api.json format from https://app.apibuilder.io/doc/apiJson

description: A JSON schema URL

description: The human readable name of this service. Used for display, and as the basis for generating a unique key for URL.

description: Optionally specify the specific version of API Builder for which your service is written. If not provided, we automatically default to the current production version.

description: Optionally specify additional metadata about this service (e.g. contact info, license).

description: Specifies the namespace for this service. Namespace is primarily used when other services import definitions from your service and in the code generators when defining things like package names. If not specified, we will automatically generate a namespace based on [organization namespace].[formatted service name].[major version number]. Note that by default API Builder includes the major version number in the package name which allows service authors and clients to interact with multiple versions of the service where changes have been made in a non backwards compatible way.

description: The base URL where this service is hosted. Must start with http.

description: optional description for what this service provides. Supports GFM.

description: JSON Array defining any other services whose schema definitions we would like to import into our service.

description: JSON Array defining any HTTP Headers that the service understands or expects.

description: JSON object defining all of the enums in this API. The key of each object is the enum name.

description: JSON object defining all of the models in this API. The key of each object is the model name.

description: JSON object defining all of the resources in this API. The key of each object is the name of a type that this resource represents. The type must be the name of a model or an enum.

description: JSON object defining all of the annotations in this API. The key of each object is the annotation name.

title: API Builder Schema


title: ExampleUseCase

description: Use case base class

title: Name

title: Description

title: Code

title: Tactics

enum:
Reconnaissance
Resource Development
Initial Access
Execution
Persistence
Privilege Escalation
Defense Evasion
Credential Access
Discovery
Lateral Movement
Collection
Exfiltration
Command and Control
Impact

title: Tags

required: name description

title: Detection

description: Detection base class

title: Name

title: Url

required: name url

title: Resource

description: External reference base class

title: Name

title: Url

description: LOOBin base class

title: Name

description: Name of the LOOBin

title: Author

description: Author of the LOOBin

title: Short Description

description: A short description of the LOOBin.This will display in the LOOBin card list and the LOOBins website search results.

title: Full Description

description: A full description of the LOOBin.This will display on the LOOBin's single page.

title: Created

description: Date the LOOBin was created

format: date

title: Example Use Cases

description: A list of example use cases for the LOOBin

$ref: #/definitions/ExampleUseCase

title: Paths

description: A list of paths to the LOOBin

title: Detections

description: A list of detections for the LOOBin

$ref: #/definitions/Detection

title: Resource

description: A list of useful resources for the LOOBin

$ref: #/definitions/Resource

title: Acknowledgements

description: Acknowledgements for the LOOBin

title: LOOBin


commands.json

description: The friendly name of the command.

description: The name of the executable file name. Example: "cmd.exe".

description: Specify a relative or absolute directory path.

description: The arguments to pass to the executable file.

description: A Visual Studio event that a command can be bound to.

description: Schema for bundleconfig.json files

description: A list of commands.

description: Specify any Visual Studio event bindings.

$ref: #/definitions/vsbindings


babelrc.json

$ref: #/definitions/Options

description: This is an object of keys that represent different environments. For example, you may have: `{ env: { production: { /* specific options */ } } }` which will use those options when the environment variable BABEL_ENV is set to "production". If BABEL_ENV isn't set then NODE_ENV will be used, if it's not set then it defaults to "development"

description: Include the AST in the returned object

description: Attach a comment after all non-user injected code.

description: Attach a comment before all non-user injected code.

description: Enable code generation

description: Output comments in generated output.

description: Do not include superfluous whitespace characters and line terminators. When set to "auto" compact is set to true on input sizes of >500KB.

type: string boolean

default: auto

description: A path to a .babelrc file to extend

description: Filename for use in errors etc.

default: unknown

description: Filename relative to sourceRoot (defaults to "filename")

description: ANSI highlight syntax error code frames

description: Opposite of the "only" option

description: If true, attempt to load an input sourcemap from the file itself. If an object is provided, it will be treated as the source map object itself.

type: boolean object

description: Keep extensions in module ids

description: Specify a custom name for module ids.

description: If truthy, insert an explicit id for modules. By default, all modules are anonymous. (Not available for common modules)

description: Optional prefix for the AMD module formatter that will be prepend to the filename on module definitions. (defaults to "sourceRoot")

description: A glob, regex, or mixed array of both, matching paths to only compile. Can also be an array of arrays containing paths to explicitly match. When attempting to compile a non-matching file it's returned verbatim.

description: List of plugins to load and use

description: The name of the plugin.

description: The options of the plugin.

description: List of presets (a set of plugins) to load and use

description: The name of the preset.

description: The options of the preset.

description: Retain line numbers. This will lead to wacky code but is handy for scenarios where you can't use source maps. NOTE: This will obviously not retain the columns.

description: Set sources[0] on returned source map. (defaults to "filenameRelative")

description: If truthy, adds a map property to returned output. If set to "inline", a comment with a sourceMappingURL directive is added to the bottom of the returned code. If set to "both" then a map property is returned as well as a source map comment appended.

description: Set file on returned source map. (defaults to "filenameRelative")

description: The root from which all sources are relative. (defaults to "moduleRoot")

title: JSON schema for Babel 6+ configuration files


description: A link to external metadata badge.

description: Link the user navigates to when selecting the badge.

description: The absolute URL of the badge image to be displayed.

description: Description of the badge, to be displayed on hover.

title: badge

description: A content file that describes the extension to users.

description: The path to the file in the extension.

title: content

description: An individual contribution made by an extension

description: List of constraints (filters) that should be applied to the availability of this contribution

$ref: #/definitions/ContributionConstraint

description: Description of the contribution/type

description: Fully qualified identifier of the contribution/type

description: Includes is a set of contributions that should have this contribution included in their targets list.

description: Properties/attributes of this contribution

description: List of demanded claims in order for the user to see this contribution (like anonymous, public, member...).

description: The ids of the contribution(s) that this contribution targets. (parent contributions)

description: Id of the Contribution Type

description: VisibleTo can be used to restrict whom can reference a given contribution/type. This value should be a list of publishers or extensions access is restricted too.  Examples: "ms" - Means only the "ms" publisher can reference this. "ms.vss-web" - Means only the "vss-web" extension from the "ms" publisher can reference this.

required: id targets type

title: contribution

description: Specifies a constraint that can be used to dynamically include/exclude a given contribution

description: An optional property that can be specified to group constraints together. All constraints within a group are AND'd together (all must be evaluate to True in order for the contribution to be included). Different groups of constraints are OR'd (only one group needs to evaluate to True for the contribution to be included).

description: Fully qualified identifier of a shared constraint

description: If true, negate the result of the filter (include the contribution if the applied filter returns false instead of true)

description: Name of the IContributionFilter plugin

description: Properties that are fed to the contribution filter class

description: Constraints can be optionally be applied to one or more of the relationships defined in the contribution. If no relationships are defined then all relationships are associated with the constraint. This means the default behaviour will eliminate the contribution from the tree completely if the constraint is applied.

description: Represents different ways of including contributions based on licensing

description: Description about a property of a contribution type

description: Description of the property

description: Name of the property

description: True if this property is required

$ref: #/definitions/ContributionPropertyType

description: The type of value used for this property

description: The type of value used for a property

description: A contribution type, given by a json schema

description: Description of the contribution/type

description: Controls whether or not contributions of this type have the type indexed for queries. This allows clients to find all extensions that have a contribution of this type.  NOTE: Only TrustedPartners are allowed to specify indexed contribution types.

description: Friendly name of the contribution/type

description: Describes the allowed properties for this contribution type

description: Base class for an event callback for an extension

description: The uri of the endpoint that is hit when an event occurs

description: Collection of event callbacks - endpoints called when particular extension events occur.

$ref: #/definitions/ExtensionEventCallback

description: Optional.  Defines an endpoint that gets called via a POST request to notify that an extension disable has occurred.

description: Optional.  Defines an endpoint that gets called via a POST request to notify that an extension enable has occurred.

description: Optional.  Defines an endpoint that gets called via a POST request to notify that an extension install has completed.

description: Optional.  Defines an endpoint that gets called via a POST request to notify that an extension uninstall has occurred.

description: Optional.  Defines an endpoint that gets called via a POST request to notify that an extension update has occurred.

description: Optional.  Defines an endpoint that gets called via a POST request to notify that an extension install is about to occur.  Response indicates whether to proceed or abort.

description: For multi-version extensions, defines an endpoint that gets called via an OPTIONS request to determine the particular version of the extension to be used

description: How an extension should handle including contributions based on licensing

description: A list of contributions which deviate from the default licensing behavior

$ref: #/definitions/LicensingOverride

description: Path to resource on disk, which can be relative to your root directory.

description: (optional) Set to true if you want your file to be URL-addressable. Defaults to false.

description: (optional) Path to the resource within the package. Defaults to the relative path on disk from your root directory.

description: (optional) MIME type of the file. Defaults to a best guess based on the file extension and OS settings.

description: (optional) Specify the value of the Type attribute of the asset entry in the VSIX manifest. Can also be an array of strings, in which case multiple asset entries get added for this file. Defaults to the packagePath.

description: (optional) Language of this asset. Localized files are served based on the Accept-Language header. Leave blank to signify this file is in the default (or fallback) language. Localized versions of the same file should have the same assetType.

title: file

description: Maps a contribution to a licensing behavior

description: How the inclusion of this contribution should change based on licensing

description: Fully qualified contribution id which we want to define licensing behavior for

description: The absolute URL of the link.

title: link

title: target

description: Base class for extension properties which are shared by the extension manifest and the extension model

description: Array of links to external metadata badges like TravisCI, Appveyor, and so on, from the approved badges sites.

$ref: #/definitions/Badge

description: Uri used as base for other relative uri's defined in extension

description: Dictionary of brand-related properties.

description: Primary color of the extension or publisher; can be a hex (#ff00ff), RGB (rgb(100,200,50)), or supported HTML color names (blue).

description: Complements the color; use dark for dark branding colors, or light for lighter branding colors.

enum: dark light

title: branding

description: Array of strings representing the categories your extension belongs to. At least one category must be provided and there's no limit to how many categories you may include. Valid values: Azure Repos, Azure Boards, Azure Pipelines, Azure Test Plans, and Azure Artifacts.

enum:
Azure Repos
Azure Boards
Azure Pipelines
Azure Test Plans
Azure Artifacts

description: List of shared constraints defined by this extension

description: Dictionary of content files that describe your extension to users.

$ref: #/definitions/Content

title: content

description: List of contribution types defined by this extension

$ref: #/definitions/ContributionType

description: List of contributions made by this extension

$ref: #/definitions/Contribution

description: List of explicit demands required by this extension

description: A few sentences describing the extensions. Limited to 200 characters.

description: Collection of endpoints that get called when particular extension events occur

description: Secondary location that can be used as base for other relative uri's defined in extension

description: The files section is where you reference any files you wish to include in your extension.

$ref: #/definitions/File

description: Dictionary of icons representing the extension.

description: 128x128 pixels

description: The extension's identifier.

description: Language Culture Name set by the Gallery

$ref: #/definitions/ExtensionLicensing

description: How this extension behaves with respect to licensing

description: Version of the extension manifest format/content. Should be 1.

description: A short, human-readable name of the extension. Limited to 200 characters.

description: Dictionary of links that help users learn more about your extension, get support, and move.

description: The identifier of the publisher. This identifier must match the identifier the extension is published under.

description: Dictionary of properties describing the source code repository for the extension.

description: Type of repository. Example: git.

description: Absolute URL of the repository.

description: Default user claims applied to all contributions (except the ones which have been specified restrictedTo explicitly) to control the visibility of a contribution.

description: List of all oauth scopes required by this extension

description: Array of images that couldn't be included in your content.

description: The ServiceInstanceType(Guid) of the VSTS service that must be available to an account in order for the extension to be installed

description: Array of string tags to help users find your extension.

description: The products and services supported by your integration or extension.

description: A string specifying the version of an extension. Should be in the format major.minor.patch.


bower.json

description: Any property starting with _ is valid.

description: The name of your package.

description: Help users identify and search for your package with a brief description.

description: A semantic version number.

description: The primary acting files necessary to use your package.

description: SPDX license identifier or path/url to a license.

description: A list of files for Bower to ignore when installing your package.

description: Used for search by keyword. Helps make your package easier to discover without people needing to know its name.

description: A list of people that authored the contents of the package.

description: URL to learn more about the package. Falls back to GitHub project if not specified and it's a GitHub endpoint.

format: uri

description: The repository in which the source code can be found.

description: Dependencies are specified with a simple hash of package name to a semver compatible identifier or URL.

description: Dependencies that are only needed for development of the package, e.g., test framework or building documentation.

description: Dependency versions to automatically resolve with if conflicts occur between packages.

description: If you set it to  true  it will refuse to publish it. This is a way to prevent accidental publication of private repositories.

description: Used by grunt-bower-task to specify custom install locations.

description: The types of modules this package exposes

type: array string

enum: amd es6 globals node yui

title: JSON schema for Bower configuration files


importmap.json

description: The Imports field

description: The Scopes field

title: JSON schema for Import Maps files


function.json

enum: in out inout

enum: string binary stream

description: The data type hint for the binding parameter (string, binary, or stream).

required: name type direction

enum: serviceBusTrigger serviceBus blobTrigger blob manualTrigger eventHubTrigger eventHub timerTrigger queueTrigger queue httpTrigger http mobileTable documentDB table notificationHub twilioSms sendGrid sql sqlTrigger kusto

description: The service bus queue to monitor (if using a queue)

description: The service bus topic to monitor (if using a queue)

description: The topic subscription name

description: An app setting (or environment variable) with the service bus connection string to be used by this binding.

description: The permission level of the service bus connection string used by this binding.

enum: manage listen send

description: The path to the blob container

description: An app setting (or environment variable) with the storage connection string to be used by this binding.

description: The event hub path.

description: The event hub connection string setting.

description: The event hub consumer group.

enum: one many

description: The cardinality hint for the input binding parameter (single message or array of messages).

description: A cron expression of the format '{second} {minute} {hour} {day} {month} {day of week}' to specify the schedule.

description: When true, your timer function will be invoked immediately after a runtime restart and on-schedule thereafter.

description: When true, schedule will be persisted to aid in maintaining the correct schedule even through restarts. Defaults to true for schedules with interval >= 1 minute.

description: The queue name.

description: The function HTTP route template.

description: The type of WebHook handled by the trigger (if handling a pre-defined WebHook).

default: function

enum: anonymous function admin

description: The function HTTP authorization level.

enum: get post delete head patch put options trace

description: This is the name of the table within your Mobile App to which data will be written.

description: This is the app setting name that specifies the URL of your Mobile App.

description: This is app setting name that specifies the API Key for your Mobile App.

description: This is the id for the record to retrieve.

description: This is the connection string for your DocumentDB account.

description: This is the name of the database within your DocumentDB account to which data will be written.

description: This is the name of the collection within your database to which data will be written.

description: This is the query to run against the collection.

description: When true, your database and collection will be created automatically.

description: The name of the storage table.

description: The partition key.

description: The table row key.

description: The number or records to retrieve.

description: A filter expression to be applied when retrieving rows.

description: The tag to send the notification to.

description: The name of the notification hub.

description: The name of the app setting which contains the notification hub connection string.

description: The notification platform to target. Sends template notification if platform is omitted.

enum: apns adm gcm wns mpns

description: The name of the app setting which contains your Twilio Account Sid.

description: The name of the app setting which contains your Twilio authentication token.

description: The phone number the SMS text is sent to.

description: The phone number the SMS text is sent from.

description: Optional body of SMS text message.

description: The name of the app setting which contains your SendGrid api key.

description: The email address to send to.

description: The email address to send from.

description: The subject of the email.

description: The text of the email.

description: The name of the app setting that contains the SQL connection string used to connect to the database.

description: The name of the table to be monitored for changes.

description: Either a query string or the name of a stored procedure to execute.

enum: text storedProcedure

description: Whether the commandText is a query (text) or a stored procedure (storedProcedure).

description: The parameters to the query or stored procedure.

const: sql

const: out

description: The name of the table into which rows will be upserted.

description: Name of the app setting that contains the kusto connection string used to connect to kusto.

description: Name of the database within your kusto account to which data will be read/written.

description: A managed service identity that has to be attached to use the bindings.

description: The Kusto command to execute.Can be a KQL query or a KQL function with optional parameters.

description: The parameters to the query or function. Named parameters are of the form @paramName=paramValue.

description: The table to ingest the data into.

description: An ingestion mapping ref that points to the mapping created in kusto and referenced in ingestion (optional).

description: Dataformat to use in ingestion.The default dataformat is `multijson/json`. This has been tested for text formats

description: If set to true, marks the function as disabled (it cannot be triggered).

description: If set to true, the function will not be loaded, compiled, or triggered.

description: Optional path to function script file.

description: Optional named entry point.

enum: attributes config

description: For C# precompiled functions only. If set to 'attributes', use WebJobs attributes to specify bindings. Otherwise, use the 'bindings' property of this function.json.

description: Retry policy of function execution failures.

description: Retry strategy to use for retrying function executions

enum: exponentialBackoff fixedDelay

default: exponentialBackoff

description: The maximum number of retries allowed per function execution. -1 means to retry indefinitely.

description: Value indicating the delayInterval for function execution retries when using FixedDelay strategy.

description: Value indicating the minimumInterval for function execution retries when using ExponentialBackoff strategy.

description: Value indicating the maximumInterval for function execution retries when using ExponentialBackoff strategy.

description: A list of function bindings.

$ref: #/definitions/dynamicBinding

$ref: #/definitions/serviceBusBinding

$ref: #/definitions/blobBinding

$ref: #/definitions/manualTriggerBinding

$ref: #/definitions/eventHubBinding

$ref: #/definitions/timerTriggerBinding

$ref: #/definitions/queueBinding

$ref: #/definitions/httpBinding

$ref: #/definitions/mobileBinding

title: JSON schema for Azure Functions function.json files