view release on metacpan or  search on metacpan

script/gu  view on Meta::CPAN

 ["no","normal","all"]

This will be passed to C<git status> in the C<-u> option.


=back

=head1 COMPLETION

This script has shell tab completion capability with support for several
shells.

=head2 bash

To activate bash completion for this script, put:

 complete -C gu gu

in your bash startup (e.g. F<~/.bashrc>). Your next shell session will then
recognize tab completion for the command. Or, you can also directly execute the
line above in your shell to activate immediately.

It is recommended, however, that you install modules using L<cpanm-shcompgen>
which can activate shell completion for scripts immediately.

=head2 tcsh

To activate tcsh completion for this script, put:

 complete gu 'p/*/`gu`/'

in your tcsh startup (e.g. F<~/.tcshrc>). Your next shell session will then
recognize tab completion for the command. Or, you can also directly execute the
line above in your shell to activate immediately.

It is also recommended to install L<shcompgen> (see above).

=head2 other shells

For fish and zsh, install L<shcompgen> as described above.

=head1 CONFIGURATION FILE

This script can read configuration files. Configuration files are in the format of L<IOD>, which is basically INI with some extra features.

By default, these names are searched for configuration filenames (can be changed using C<--config-path>): F</home/u1/.config/gu.conf>, F</home/u1/gu.conf>, or F</etc/gu.conf>.

All found files will be read and merged.

To disable searching for configuration files, pass C<--no-config>.

To put configuration for a certain subcommand only, use a section name like C<[subcommand=NAME]> or C<[SOMESECTION subcommand=NAME]>.

You can put multiple profiles in a single file by using section names like C<[profile=SOMENAME]> or C<[SOMESECTION profile=SOMENAME]> or C<[subcommand=SUBCOMMAND_NAME profile=SOMENAME]> or C<[SOMESECTION subcommand=SUBCOMMAND_NAME profile=SOMENAME]>....

You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...

You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...

To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:

 [plugin=DumpArgs]
 -event=before_validate_args
 -prio=99
 
 [plugin=Foo]
 -event=after_validate_args
 arg1=val1
 arg2=val2

 

which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.

List of available configuration parameters:

=head2 Common for all subcommands


=head2 Configuration for subcommand clone-to-bare

 dir (see --dir)
 target_dir (see --target-dir)

=head2 Configuration for subcommand dir

 dir (see --dir)

=head2 Configuration for subcommand du-committing

 include_untracked (see --exclude-untracked)

=head2 Configuration for subcommand du-untracked

 detail (see --detail)

=head2 Configuration for subcommand info

 dir (see --dir)

=head2 Configuration for subcommand ls-committing-large

 detail (see --detail)
 include_untracked (see --exclude-untracked)
 max_size (see --max-size)

=head2 Configuration for subcommand post-commit

 dir (see --dir)

=head2 Configuration for subcommand pre-commit

 dir (see --dir)

=head2 Configuration for subcommand rh

 dir (see --dir)
 name (see --name)

=head2 Configuration for subcommand run-hook

 dir (see --dir)
 name (see --name)

=head2 Configuration for subcommand split-commit-add-untracked

 max_size (see --max-size)

=head2 Configuration for subcommand status

 untracked (see --untracked)

=head1 ENVIRONMENT