It would be great to make use of the new syntect API to detect when a syntax definition has some context references (specifically push/set targets - missing includes are not such a problem and can be just treated as warnings) which couldn't be linked/resolved and fail the CI build. sharkdp/bat#915 (comment)

• Gitea version (or commit ref): 1.13 (Codeberg), 1.15 (try.gitea.io)
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes https://try.gitea.io/30repos (feel free to join this org as admin)

Description

The paging of repos is broken in the user dashboard with (n)*15 repos, n >= 2.
So wi

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

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

Is your feature request related to a problem? Please describe.
Hey! Netlify-CMS has been great so far, thanks! One thing i've found when working with the content authors is if the compile fails there is no way for a content author to know, it just shows Check for preview forever.

Describe the solution you'd like
When the GitHub status is failed, we should show some message instead of

Describe the feature or problem you’d like to solve

Microsoft released Windows Terminal Preview yesterday. It would be nice if GitHub Desktop was able to detect it.

Proposed solution

Adds an option to the shells available to use.

Additional context

N/A

Ref #94. It might be better for the output to say something like

added: foo (binary file)

than the current

Binary files /dev/null and b/foo differ