Git

Git is the most widely used version control system, which allows for the tracking and managing of source code over time. It was designed for collaboration and built to be flexible, secure and efficient.
Here are 11,699 public repositories matching this topic...
As far as I can tell bat as a library only supports writing to stdout, I'm interested in seeing if I can integrate bat
with color-backtrace
/color-spantrace
and eyre
. To do this I need bat to write to a std::fmt::Formatter
and return a fmt::Result
instead of printing to stdout
(i assume?) and returning a bat::error::Error
.
So assuming I'm not misreading the docs...
Proposal
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)
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.
Currently we are using ronn to convert markdown docs to man pages and html files. Ronn is not longer maintained so we want to use ronn-ng instead.
There are two blocking issues about ronn-ng:
-
Updated
Jun 2, 2020 - Perl
-
Updated
Mar 4, 2019
Describe the bug
If you use github as backend the following basic setup is required:
- run your own github auth server backend (see https://github.com/vencax/netlify-cms-github-oauth-provider) - https://mygithub-auth-backend.org as an example
-create oauth app in github and configure callback url pointing to your github auth server backend (https://mygithub-auth-backend.org/callback) - set
-
Updated
Jul 15, 2020 - PHP
Currently, if look at the windows_e2e tests on circle under the write e2e files
step, you will see this warning:
Error autodetecting timing type, falling back to weighting by name. Autodetect no matching filename or classname. If file names are used, double check paths for absolute vs relative.
Example input file: "e2e\\api\\add-many.e2e.1.ts"
Example file from timings: "C:\\Users\\****
-
Updated
Jul 17, 2020 - TypeScript
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@
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).
-
Updated
Jul 8, 2020 - Shell
It would be great if I could run brew install ungit
on OSX. This would install a plist which would automatically start ungit on login.
More resources:
- https://github.com/Homebrew/brew/blob/master/docs/Formula-Cookbook.md
- https://github.com/Homebrew/brew/blob/master/docs/How-to-Create-and-Maintain-a-Tap.md
- https://github.com/FredrikNoren/ungit/wiki/Startup-Script-for-Mac-OS-X
Thank
Describe the issue
What's the syntax to properly exclude the contents of directories called foo
(and their sub-directories) from LFS fetching but still download LFS files with the same name ('foo')?
git config lfs.fetchexclude "foo"
will I assume exclude directories calledfoo
and files calledfoo
git config lfs.fetchexclude "foo/"
may do the same as the code appears to [str
-
Updated
Jul 17, 2020 - Vue
-
Updated
Jul 17, 2020 - C
-
Updated
Jul 17, 2020 - Python
-
Updated
Jul 16, 2020 - JavaScript
Created by Linus Torvalds
Released April 7, 2005
- Organization
- git
- Website
- git-scm.com
- Wikipedia
- Wikipedia
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