See https://github.com/yuin/goldmark/

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)

My problem

I am tweaking some templates so that I can see in depth license information. It seems to me the best way to do this would have the server figure it out via templating (rather than using javascript to parse the license and compare it to all other possible known license). I couldn't find anything helpful regarding templating in docs.gitea.io. Searching the gitea repo for licenses r

I use bat to preview files in fzf. When bat is called on a binary file, it will display a warning:

$ bat foo.pdf 2> /dev/null
[bat warning]: Binary content from file 'foo.pdf' will not be printed to the terminal (but will be present if the output of 'bat' is piped). You can use 'bat -A' to show the binary file contents.

As you can see

Is there any place to read about "edge" setup with Yarn 2 and pure PnP project?
It seems like everything in my side is installed as recommended in various places, still, hooks are not triggered and no any errors provided.
I would be grateful for a clean and precise section in the documentation on how to set up Husky in pure Berry PnP project.

The git-tips project is amazing! It was a great idea to make a usable JSON file. So I thought why not harness the tips.json and make a CLI - https://github.com/nirajpandkar/gtip

Further by tinkering the ~/.bashrc file one would be greeted with a new git-tip every time he/she opens the terminal. I think this'll help people to easily learn new git tips and tricks!

Feedbacks/Suggestions/Cr

Is your feature request related to a problem? Please describe.
I am trying to change some of default lazygit behavior, e.g. have a --oneline graph in commits view. I could not find any info about configuring lazygit. The only glimpse of this I had was at 11:20 in the 15 lazygit features youtube video.

Describe the solution you'd like
I would expec

it could be interesting to allow coauthor to be complete with previous authors.

The idea is to use git authors --list in _git_coauthor completion function in zsh and bash so we don't need to write name and email address in each call.

Currently d-s-f doesn't work correctly with git log --graph. Among other things, the headers are not formatted correctly, and the setting to ignore the leading +/- is not respected. Example:

git log --decorate --oneline  -1 --stat -p  git.c

git log --decorate 

Problem

When using git-history with a base repo url you get the startpage of githistory.xyz which isn't very useful by itself.
I'd suggest redirecting to the RegEx:(?i)readme(\.md|\.rst|\.txt)? file on the master branch.

Example

https://github.githistory.xyz/babel/babel/
--> https://github.githistory.xyz/babel/babel/blob/master/README.md

equally with gitlab:
<https://gitlab

Posting here at the suggestion from the chat.

NetlifyCMS resolves regular filename collisions by appending a numeric index, e.g.

/entries/concert.md
/entries/concert-1.md   # different concert, fine
/entries/concert-2.md   # ditto

Folder collections

I'm using the folder collections path BETA featu

Description

Bit does not generate docs for React TS components.

for example:

https://bit.dev/eden/react-ts-demo

Specifications

• Bit version: 14.7.4
• Node version: 10.15.3
• npm / yarn version: 6.4.1 / 1.16.0
• Platform: macOS
• Bit compiler (include version): bit.envs/compilers/react-typescript@3.1.44
• Bit tester (include version):

Context and additional inf

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

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

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

root@syzoj-test-vm:~/syzoj-ng-app# commitizen init cz-conventional-changelog --yarn --dev --exact
Attempting to initialize using the npm package cz-conventional-changelog
yarn add v1.19.0
[1/4] Resolving packages...
[2/4] Fetching packages...
error Incorrect integrity when fetching from the cache
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
root@

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

As suggested by @bk2204's comment, this issue is a follow-up to #3123.

There, I asked that the warning for the command git lfs migrate import --include="*.csv" (or other extensions) about deleting uncommitted changes should be a lot more flashy! Per

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

Would be great to get a quick help file for the command.

$ git help standup
No manual entry for git-standup
$ git standup --help
No manual entry for git-standup