Crates.io | codeberg-cli |
lib.rs | codeberg-cli |
version | 0.4.6 |
source | src |
created_at | 2023-02-08 18:46:44.837463 |
updated_at | 2024-11-12 11:46:03.648802 |
description | CLI Tool for codeberg similar to gh and glab |
homepage | https://codeberg.org/Aviac/codeberg-cli |
repository | https://codeberg.org/Aviac/codeberg-cli |
max_upload_size | |
id | 780120 |
size | 559,318 |
### 2024-04-20
`codeberg-cli` is un-deprecated since `fjo` development came to a halt before reaching feature pairity and I think we're better off including the findings here.
### End of 2023
We are thrilled to share a pivotal update on our software project. Thanks to recent developments, our project is now compatible with all Forgejo instances, not limited to Codeberg. As part of this expansion, the primary development focus will shift to our forked repository, [fjo](https://codeberg.org/VoiDD/fjo) in the future.
Rest assured, `codeberg-cli` will remain active. Our plan is to seamlessly incorporate new changes from the forked project here. We'll continue to make small adjustments to ensure smooth use, particularly for Codeberg, such as optimizing default values and Codeberg-specific features.
We appreciate your ongoing support and anticipate delivering even more enhancements soon.
CLI Tool for Codeberg similar to gh
and glab
.
For API communication reasons, the package depends on openssl
package. Please make sure to install this with your systems respective package manager before continuing.
The easiest way to install the berg
command is using cargo. (If you haven't installed rust/cargo yet, take a look here)
Clone the repo and install berg
with
cargo install --path .
Anywhere, just run
cargo install codeberg-cli
Run the following:
sudo xbps-install codeberg-cli
Run the following:
nix-shell -p codeberg-cli
or
nix develop nixpkgs#codeberg-cli
After that, the berg
command should be available for you. Check it with berg -V
berg 0.4.0
Run berg -h
for the help menu. Each subcommand also has it's own help menu
Codeberg CLI app
Usage: berg [OPTIONS] <COMMAND>
Commands:
api API subcommands
auth Authentication subcommands
config Config subcommands
user User subcommands
issue Issue subcommands
pull Pull request subcommands
label Label subcommands
repo Repository subcommands
milestone Milestone subcommands
notification Notification subcommands
completion Print completion script
help Print this message or the help of the given subcommand(s)
Options:
--non-interactive Whether or not to disable all interactive features.
In this case arguments have to be provided in the console!
-h, --help Print help
-V, --version Print version
If you want to use this tool with instances of forgejo other than codeberg.org
this is possible through extra configuration either through files or through environment variables:
berg config generate
. Please take a look at the command line options via the --help
flag. Please also note that you can check the current configuration values and where they are sourced from via berg config info
.berg config info
. The environment variable names are the option names prefixed by BERG_
. Example: base_url
in config files is equivalent to BERG_BASE_URL
in environment variablesPlease note that the environment variables take precedence over the config file options. Also: There exist several visibility ranges for config files (local vs. global) and berg
tries to resolve this recursively starting from the most local path walking upwards. Local configurations take precedence over global ones.
BERG_BASE_URL=localhost:8000 berg auth login
Please take a look at CONTRIBUTING.md before opening PRs. We can't accept PRs which don't stick to the guidelines.
The development of codeberg-cli
has gone to sleep several times due to me being busy. I just want to encourage you checking out similar other projects which are trying to achieve some similar goals:
fjo
- A collective approach of re-writing codeberg-cli
forgejo-cli
- A CLI application for interacting with forgejo in general