🐞 Bug report

Command (mark with an x)

Hi, I've found the following cheatsheet :

In the README you explain that there must be an edit button in the page and a github button to access the sheet but as you can see it doesn't appear here.

Thx ;)

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...

GenMarkdownTreeCustom has a way to a header (filePrepender arg), however there is not a first class way to add a footer.

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

• It took me a while to understand this error message. I thought it meant I didn't have Node 15 locally
• It'd be great to link all error messages to markdown files in the repo so that we can expand and improve them over time

It's always a good idea to work on documentation. I think it would also be good to restructure the README:

• Add a quick link section at the top of the readme (see https://github.com/sharkdp/bat)
• Extend the tutorial (rename "How to use"?)
• Move the "Parallel command execution" section inside the "How to use" section). See also: #605
• Move "Installation" section below the

...this boilerplate is awesome, thank you for sharing it guys 👍

This is a meta issue to describe ongoing attention that should be devoted to tests. I don't want anyone to do this in a single commit or even a single PR, it's something that anyone can pick up one file, or even one part of a file, at a time. The later tasks about reorganizing will be easier once the earlier tasks are done, but will still require a good amount of familiarity and planning.

The t

Currently, each argument to fx treated as an anonymous function. Here is an example:

fx 'groupBy("commit.author.name")' 'mapValues(size)' toPairs 'sortBy(1)' reverse 'take(10)' fromPairs

But this requires a lot of ' quotes. My idea is to split the argument by whitespaces . So next will be possible to write:

fx 'groupBy("commit.author.name") mapValues(size) toPairs so