Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Creating a symlink called README.md in the repository root (that points to another markdown file) should render a preview on the repository web page.

At the moment, it only displays the name of the symlink in the preview pane.
See screenshot below.

On Github a README symlink to a

One common use case for project maintainers is to update a broken pull request which was made by someone else.

Hub should be able to help maintainers doing the following steps:

• grab a pull request
• update the pull request (rebase or other change)
• update the pull request (aka pushing it)

I am currently working on a custom notification system involving Gitea. The details of this setup aren't really relevant to the topic at hand; there'll be an HTTP server that takes events via webhooks and produces notifications to send elsewhere.

My problem: there's hardly any documentation on webhooks. The doc page merely lists the different hooks avail

Line wrapping seems to be disabled when piping to another process, even when forced with --wrap=character.

$ echo 123456789abcd > /tmp/file
$ bat --style plain --terminal-width 10 --wrap=character /tmp/file
123456789a
bcd
$ bat --style plain --terminal-width 10 --wrap=character /tmp/file | command cat
123456789abcd

Using Husky 3.1.0

This issue is about this message:

Warning: Setting pre-commit script in package.json > scripts will be deprecated
Please move it to husky.hooks in package.json, a .huskyrc file, or a husky.config.js file
Or run ./node_modules/.bin/husky-upgrade for automatic update

My package.json currently looks like this:

  "scripts": {
    "precommit": "yarn lin

Just a couple sentences above the TOC that would at least include the git version on which these were tested (see also #47). Many operating systems are pinned on older versions with varying behavior. Ideally each command would have an "added in x.x" clause, but I understand if that's going a bit too far.

This is a very very minor quibble, but I keep finding myself stumped when I'm staging changes line-wise and want to commit --- intuitively, I would just want to press c from the staging view, but instead I have to go back to the file menu with Esc and then press c. A bit unnecessary in my opinion, especially since c is not mapped to anything else in the staging view.

So if at all poss

According to
https://discourse.drone.io/t/github-claims-that-merge-refs-are-undocumented-feature/1100

The /merge refs are created only to check the mergeability. If a branch is already merged, the ref will be deleted. If no one visits the pull request page or uses the API to trigger the mergeability check, the ref will not update.

Although we could manually trigger the ref rebuild via visi

Original

diff --git a/a b b/a b
new file mode 100644
index 0000000..e69de29

So-Fancy:

─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
added: a
───────────────────────────────────────────

Long lines of text get truncated.

For example, In https://gitlab.githistory.xyz/nyanpasu64/exotracker-cpp/blob/master/README.md, the Credits section has some long lines which get truncated. This is especially visible at timestamp on Sun Oct 13 2019.

I think the best solution is to either add horizontal scrolling (which interferes with the current keyboard shortcuts of using left/right to

Related issue: netlify/netlify-cms#2947

Screenshots from that issue:

![Screen Shot 2

Description

Bit know to parse javascript, React and Vue component documentation, but not do it for Angular component.

Specifications

• Bit version: 14.4.3
• Node version: 12.7.0

Context and additional information

Angular button component for example:
https://bit.dev/primefaces/primeng/button

现存什么问题没有很好被解决

In the docker-compose documentation:

https://docs.docker.com/compose/compose-file/#links

Warning: The --link flag is a legacy feature of Docker. It may eventually be removed. Unless you absolutely need to continue using it, we recommend that you use user-defined networks to facilitate communication between two containers instead of using --link. One feature that us

I'm complete noob. I don't know anything about Node or npm.
I came here in search of easy Git GUI.
I have read the Readme of this project
I have no idea how to install it on Windows

where do I put commands? isn't "sudo" the linux command? please help

Describe the bug

When a diff highlights a portion of the changed line in a typescript file the text is much harder to see with the dark theme than the light theme.

Version & OS

• Version 2.2.2-beta3
• Windows 10

Steps to reproduce the behavior

1.Modify a typescript file by adding an annotation to a line
2. View the diff in GitHub Desktop

Expected behavior

To

While the documentation from https://github.com/jonas/tig/blob/master/tigrc#L144-L158 is extremely useful it appears to document one use case which i find likely to be desired:

Run command in background and display its output only if it failed (non zero return code).

Feature request

Similar to the virtualenv feature, it'd be great if this was extended into node, and showed the current version being used via nvm or similar tools

The npm list command shows me an error, but everything seems to be working correctly

OS: Linux Mint 19.2
nvm: 0.35.0
node: v10.16.3
npm: 6.12.0
commitizen: 4.0.3
cz-conventional-changelog: 3.0.2

cat .czrc 
{ "path": "cz-conventional-changelog" }

Issue

Impacted version: 4.33.0

Deployment mode: standalone app

Repro steps:

1. Wiki -> New Page
2. Fill in each item and click "Save" button.
   • Page name: title+
   • Content: aaa
3. Redirect to the edit page.
   • Page name: title instead of title+
   • Content: (blank)

As + is decoded to whitespace, should it be treated as an invalid character he

Describe the issue
@bk2204 Currently only arm64, amd64 and i386 are being put on the releases for git-lfs. This creates an issue when going to use other architectures like s390x and ppc64le, since we have to build from source.

It would be great to have s390x and ppc64le binaries added to releases for convenience.

Building s390x binary using the build from source directi

Reproduction steps

Visit https://libgit2.org/libgit2/#HEAD. Look for git_repository_set_refdb. It is not present, nor are any of the functions I checked from include/git2/sys/repository.h.

Version of libgit2 (release number or SHA1)

Whatever the website is at as of Sep 6, 2019. (Perhaps the website should provide a sha indicating what HEAD is?)

I think the work you've done on this is amazing. Seems like a great project, but your README is a bit bloated and hard to decipher. Might I suggest you condense it down into a set of readable chunks and maybe link off to the wiki for the more detailed bits.

Its only my opinion, but I find that answering the following questions, in order, helps to simplify docs.

• who? - who wrote the p

I love this project, and I use it daily. In this daily usage, I've identified just one possible improvement: the addition of the branch name to the commit message. I work in multiple branches for different features, and need to reference the branch name in my daily standup. If git standup included a flag that enabled outputting the branch name before the commit (i.e. `[branch_name] Commit mess

I am relatively new to GitHub and even newer to Wiki.js & struggled for several hours to properly configure port 80 and 443 proxying to get the wiki my colleague built for our company to automatically work with port 80 & 443 and automatically redirect to port 443 and have it work properly with the wiki node proxy.

I would like to suggest a quick addition of a full proper nginx config (example b