Crates.io | gitlab-tui |
lib.rs | gitlab-tui |
version | 0.1.2 |
source | src |
created_at | 2023-07-11 23:39:52.123711 |
updated_at | 2023-07-12 11:44:46.289818 |
description | A terminal based UI for interacting with your gitlab issues and merge requests |
homepage | https://github.com/NiklasTreml/gitlab-tui |
repository | https://github.com/NiklasTreml/gitlab-tui |
max_upload_size | |
id | 914169 |
size | 90,358 |
A TUI app for interacting with GitLab issues and merge requests.
You can use Cargo to download, compile, and install Gitlab TUI on your machine:
cargo install gitlab-tui
To authenticate the GitLab API, Gitlab TUI uses the same .netrc
config that Git uses for HTTP cloning. If you have already set up Git with .netrc
, there is a good chance it will work immediately. If not, you will need to create one:
Create an API token in GitLab with read-api
scope.
Create a .netrc
file:
On Linux and macOS:
touch ~/.netrc
On Windows:
New-Item ~/.netrc
Create an entry for your GitLab instance:
For GitLab.com:
machine gitlab.com
login __token__
password <YOUR_TOKEN>
For self-hosted GitLab:
machine <YOUR_GITLAB_INSTANCE>
login __token__
password <YOUR_TOKEN>
That's it! Now just cd
into your repo and run gitlab-tui
. The program will parse your Git SSH or HTTP remote to figure out the GitLab API URL and fetch all issues and merge requests of your project.
The binary is called gitlab-tui
. You can bring up the UI by running it without any arguments. If you need to use a different remote than origin
, you can use the -r
flag to override the remote.