github-cmd - Yet another github CLI
This document describes version 0.003 of github-cmd (from Perl distribution App-github-cmd), released on 2018-10-09.
In ~/.config/github-cmd.conf:
login = YOUR_GITHUB_LOGIN pass = YOUR_GITHUB_PASSWORD # or access_token = YOUR_API_TOKEN
or just run github-cmd, which will prompt you login+pass and write them to configuration.
github-cmd
% github-cmd get-user % github-cmd get-user perlancar
% github-cmd list-repos % github-cmd list-repos -l % github-cmd list-repos --start 100 % github-cmd get-repo perl-App-github-cmd % github-cmd get-repo --user perlancar perl-App-github-cmd % github-cmd repo-exists perl-App-github-cmd 1 % github-cmd repo-exists --user perlancar perl-App-github-cmd-FOO 0 % github-cmd create-repo foo
EARLY RELEASE. More commands coming soon.
This is yet another Github CLI, written in Perl using the Perinci::CmdLine framework and Net::GitHub::V3 API client.
Create a repository.
Get information about a repository.
Get information about a user.
List user's repositories.
Check whether a repository exists.
* marks required options.
*
Set path to configuration file.
Can be specified multiple times.
Set configuration profile to use.
Shortcut for --log-level=debug.
Choose output format, e.g. json, text.
Default value:
undef
Display help message and exit.
Set output format to json.
Set log level.
When outputing as JSON, strip result envelope.
0
By default, when outputing as JSON, the full enveloped result is returned, e.g.:
[200,"OK",[1,2,3],{"func.extra"=>4}]
The reason is so you can get the status (1st element), status message (2nd element) as well as result metadata/extra result (4th element) instead of just the result (3rd element). However, sometimes you want just the result, e.g. when you want to pipe the result for more post-processing. In this case you can use `--naked-res` so you just get:
[1,2,3]
Do not use any configuration file.
Do not read environment for default options.
Shortcut for --log-level=error.
List available subcommands.
Shortcut for --log-level=trace.
Shortcut for --log-level=info.
Display program's version and exit.
This script has shell tab completion capability with support for several shells.
To activate bash completion for this script, put:
complete -C github-cmd github-cmd
in your bash startup (e.g. ~/.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 cpanm-shcompgen which can activate shell completion for scripts immediately.
To activate tcsh completion for this script, put:
complete github-cmd 'p/*/`github-cmd`/'
in your tcsh startup (e.g. ~/.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 shcompgen (see above).
For fish and zsh, install shcompgen as described above.
This script can read configuration files. Configuration files are in the format of IOD, which is basically INI with some extra features.
By default, these names are searched for configuration filenames (can be changed using --config-path): /home/u1/.config/github-cmd.conf, /home/u1/github-cmd.conf, or /etc/github-cmd.conf.
--config-path
All found files will be read and merged.
To disable searching for configuration files, pass --no-config.
--no-config
To put configuration for a certain subcommand only, use a section name like [subcommand=NAME] or [SOMESECTION subcommand=NAME].
[subcommand=NAME]
[SOMESECTION subcommand=NAME]
You can put multiple profiles in a single file by using section names like [profile=SOMENAME] or [SOMESECTION profile=SOMENAME] or [subcommand=SUBCOMMAND_NAME profile=SOMENAME] or [SOMESECTION subcommand=SUBCOMMAND_NAME profile=SOMENAME]. Those sections will only be read if you specify the matching --config-profile SOMENAME.
[profile=SOMENAME]
[SOMESECTION profile=SOMENAME]
[subcommand=SUBCOMMAND_NAME profile=SOMENAME]
[SOMESECTION subcommand=SUBCOMMAND_NAME profile=SOMENAME]
--config-profile SOMENAME
You can also put configuration for multiple programs inside a single file, and use filter program=NAME in section names, e.g. [program=NAME ...] or [SOMESECTION program=NAME]. The section will then only be used when the reading program matches.
program=NAME
[program=NAME ...]
[SOMESECTION program=NAME]
Finally, you can filter a section by environment variable using the filter env=CONDITION in section names. For example if you only want a section to be read if a certain environment variable is true: [env=SOMEVAR ...] or [SOMESECTION env=SOMEVAR ...]. If you only want a section to be read when the value of an environment variable has value equals something: [env=HOSTNAME=blink ...] or [SOMESECTION env=HOSTNAME=blink ...]. If you only want a section to be read when the value of an environment variable does not equal something: [env=HOSTNAME!=blink ...] or [SOMESECTION env=HOSTNAME!=blink ...]. If you only want a section to be read when an environment variable contains something: [env=HOSTNAME*=server ...] or [SOMESECTION env=HOSTNAME*=server ...]. Note that currently due to simplistic parsing, there must not be any whitespace in the value being compared because it marks the beginning of a new section filter or section name.
env=CONDITION
[env=SOMEVAR ...]
[SOMESECTION env=SOMEVAR ...]
[env=HOSTNAME=blink ...]
[SOMESECTION env=HOSTNAME=blink ...]
[env=HOSTNAME!=blink ...]
[SOMESECTION env=HOSTNAME!=blink ...]
[env=HOSTNAME*=server ...]
[SOMESECTION env=HOSTNAME*=server ...]
List of available configuration parameters:
format (see --format) log_level (see --log-level) naked_res (see --naked-res)
access_token (see --access-token) description (see --description) homepage (see --homepage) login (see --login) pass (see --pass) repo (see --repo)
access_token (see --access-token) login (see --login) pass (see --pass) repo (see --repo) user (see --user)
access_token (see --access-token) login (see --login) pass (see --pass) user (see --user)
access_token (see --access-token) detail (see --detail) login (see --login) pass (see --pass) start (see --start)
Specify additional command-line options.
/home/u1/.config/github-cmd.conf
/home/u1/github-cmd.conf
/etc/github-cmd.conf
Please visit the project's homepage at https://metacpan.org/release/App-github-cmd.
Source repository is at https://github.com/perlancar/perl-App-github-cmd.
Please report any bugs or feature requests on the bugtracker website https://rt.cpan.org/Public/Dist/Display.html?Name=App-github-cmd
When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature.
App::ph - another GitHub CLI written by TOKUHIROM. It is last released in 2013 and only contains a few subcommands.
perlancar <perlancar@cpan.org>
This software is copyright (c) 2018 by perlancar@cpan.org.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
To install App::github::cmd, copy and paste the appropriate command in to your terminal.
cpanm
cpanm App::github::cmd
CPAN shell
perl -MCPAN -e shell install App::github::cmd
For more information on module installation, please visit the detailed CPAN module installation guide.