mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 09:17:30 +03:00
88085025a6
Summary: User should see no difference between scratch and non-scratch remote bookmarks. So let's make scratch bookmarks remote if remotenames is enabled. Unfortunately it requires saving scratch remote bookmarks before push/pull and restoring it afterwards because `remotenames` extension doesn't know about them. Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4036653 Tasks: 12479677 Signature: t1:4036653:1476985129:b5c1afdab4c7585c8b12c2962a4b95a56751091b |
||
|---|---|---|
| .. | ||
| integrationtests | ||
| tests | ||
| __init__.py | ||
| fileindexapi.py | ||
| indexapi.py | ||
| README | ||
| sqlindexapi.py | ||
| store.py | ||
## What is it?
This extension adds ability to save certain pushes to a remote blob store
as bundles and to serve commits from remote blob store.
The revisions are stored on disk or in everstore.
The metadata are stored in sql or on disk.
## Config options
infinitepush.branchpattern: pattern to detect a scratchbranch, example
're:scratch/.+'
infinitepush.indextype: disk or sql for the metadata
infinitepush.reponame: only relevant for sql metadata backend, reponame to put in
sql
infinitepush.indexpath: only relevant for ondisk metadata backend, the path to
store the index on disk. If not set will be under .hg
in a folder named filebundlestore
infinitepush.storepath: only relevant for ondisk metadata backend, the path to
store the bundles. If not set, it will be
.hg/filebundlestore