This is the help for the `git-override` package. To view upstream `git` help, run `git help`.
The `git-override` package provides a binary named `git` (which is displaying this help output) which will either delegate to an upstream `git` or a subcommand override executable. In the absence of any subcommand override, the arguments and behavior should behave identically to upstream git.
A subcommand override is an executable on `PATH` named `git-<subcommand>`, where `<subcommand>` is the first argument that does not begin with `-`. For example, when executed as `git --no-pager push my_branch` the `PATH` is searched for an executable named `git-push`.
A subcommand is executed with the same arguments passed to `git-override`, including the subcommand argument itself, as well as any global `git` options which appear before the subcommand. For example, if `git-push` is an override on the path, and `git-override` is executed with this command:
```
$ git --no-pager push my_branch
```
-then the executable `git-push` will receive the arguments `--no-pager push my_branch` after the executable arg.
Any override execution also has the environment variable `GIT_OVERRIDE_UPSTREAM` pointing to the executable path of the upstream `git`, which is often necessary to invoke the underlying functionality being overridden.