Skip to content

testing#3

Open
bpeabody wants to merge 643 commits intobpeabody:add-submodulefrom
twosigma:master
Open

testing#3
bpeabody wants to merge 643 commits intobpeabody:add-submodulefrom
twosigma:master

Conversation

@bpeabody
Copy link
Owner

No description provided.

bpeabody and others added 30 commits March 26, 2019 11:13
Turn off merge with bare in normal merge mode
fix #707: failed to set workdir correctly if submodule first opened i…
Add an option --no-verify for bypassing pre-commit hooks
Caveats:
* pre-commit hooks is not supported with option [--interactive]
Exec 'pre-commit' hook of each submodule before start committing
Nested urls, like cache::https://example.com/my/repo, break node's
url parsing.  So we have to manually resolve relative urls.
no longer recurse in parallel.

Recusing in parallel can create exponentially-many threads; it seems
to be extremely ineffecient.

Writing for all parents makes future lookups faster.
It's kind of annoying that we have to do this, but I've hit this a few
times for reasons I don't really understand. So let's just make the
buffer huge and hope we don't fill it.
Bumps [lodash](https://github.com/lodash/lodash) from 4.17.11 to 4.17.15.
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.11...4.17.15)

Signed-off-by: dependabot[bot] <support@github.com>
Unfortunately, we have http.postbuffer set to an astronomical value
due to https://gitlab.com/gitlab-org/gitlab/issues/17649.  This means
that high parallelism on open can cause OOMs.
geofft and others added 30 commits June 10, 2022 07:02
Make a branch for the original commit of the conflicted rebase so that
`git gc` isn't inclined to garbage-collect it.
Make hooks work with hooksPath config
Fix flaky test "rebase in a sub, was conflicted" (fixes #864)
Typos in architecture.md
If `-u` is provided to `git meta add`, do not require a path.
This more closely matches the behavior of `git add -u`.

Output of `git meta add`:
```
Nothing specified, nothing added.
hint: Maybe you wanted to say 'git meta add .'?
```

Output of `git add`:
```
Nothing specified, nothing added.
hint: Maybe you wanted to say 'git add .'?
hint: Turn this message off by running
hint: "git config advice.addEmptyPathSpec false"
```
Use 'PrintStatusUtil' in cmd/add
Tracked filepaths were undergoing relative path resolution twice
Update ci.yml to use ubuntu-18.04 instead of latest for now
implement git meta add verbose flag
reduce line length

extract logging logic to function

fix quotes

semi colon
Add no-commit option to cherry-pick
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Comments