[x] I have commented my code in hard-to-understand areas
[x] I have made corresponding changes to the documentation
Description
Fixes #147
This works by adding a file (bin/git-forgit) that acts as a bridge between forgit and git. The file takes any command, changes underscores to double colons (_ → ::), and forwards all arguments to the associated function in forgit.plugin.zsh. For example, git forgit log becomes forgit::log, and git forgit checkout_file README.md becomes forgit::checkout::file README.md.
This file should be future-proof as long as the current naming scheme continues, so it won't need to be updated every time a new command is added.
Also, this relies on the user setting an environment variable named FORGIT_STANDALONE. All new code in forgit is hidden behind this new flag, so no current users will see any change in behavior or performance when updating forgit.
Check list
Description
Fixes #147
This works by adding a file (
bin/git-forgit
) that acts as a bridge between forgit and git. The file takes any command, changes underscores to double colons (_
→::
), and forwards all arguments to the associated function inforgit.plugin.zsh
. For example,git forgit log
becomesforgit::log
, andgit forgit checkout_file README.md
becomesforgit::checkout::file README.md
.This file should be future-proof as long as the current naming scheme continues, so it won't need to be updated every time a new command is added.
Also, this relies on the user setting an environment variable named
FORGIT_STANDALONE
. All new code in forgit is hidden behind this new flag, so no current users will see any change in behavior or performance when updating forgit.Type of change
Test environment