Skip to content
#

Command line interface

cli logo

Before there were graphical user interfaces, command-line interfaces were used to issue commands to a computer. Programs that handle the user interface are called command language interpreters, often known as a shell. A CLI may give a user more control over the computer and programs they wish to execute.

Here are 23,646 public repositories matching this topic...

cli
gibfahn
gibfahn commented Jan 2, 2021

Describe the bug

When I try to fork a repo and add a new remote, it doesn't add a new remote to my current repository.

gh version 1.4.0 (2020-12-17)

Expected vs actual behavior

I expect to see a fork remote added to my repository, but nothing is added.

Logs

gh repo fork --clone=false --remote=true $(git remote get-url up)
- Forking someorg/somerepo...
ristillu
ristillu commented Feb 17, 2021

Is your feature request related to a problem? Please describe.
In our project we use git describe all the time for issue tracking. I implemented a custom command that sort of does what I want but I'm interested if you have ever thought about informational only prompts. I.e. not 'input' or 'menu', just outputting the result of something like git describe. There may be other use cases for infor

Stratus3D
Stratus3D commented Feb 10, 2019

Steps to reproduce

Run asdf. In help output a line is printed for the asdf env command:

asdf env <command> [executable]      Prints or runs an executable under a command environment

I would assume <command> is an arbitrary command. But from what I can tell needs to be a plugin name or a shim name? I'm also not sure how this differs from executing the shim directly.

FY

Created by Glenda Schroeder

Released 1965

Wikipedia
Wikipedia