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 24,926 public repositories matching this topic...

cli
shrink
shrink commented Sep 29, 2021

Describe the feature or problem you’d like to solve

dev:~$ gh secret encrypt
Paste your secret: *************
✓ Encrypted secret for `org/repository`
QkMFB+vyCCE2yT5j6Tb07doxD2xKHagI2l6AjMuwUkizN7pMGXKBVOj154Pg/hwn0PbPWFvo83z+ir25iw==

Proposed solution

Separate the encryption step and make it available as a separate command so that users can easily generate an

jkogler-cloudflight
jkogler-cloudflight commented Aug 2, 2021

Is your feature request related to a problem? Please describe.
In our company we have way too many branches remotely. Basically everybody creates new ones for every PR, and most of the time the branches don't get deleted afterwards.
That makes it very hard to check out a remote branch with lazygit, as I have to search for it. Need to know the exact PR number, ...

**Describe the solution

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