sapling/hgext/infinitepush
Jun Wu 51c92b569d hgext: use in-core revive API
Summary: No longer need to check inhibit.

Reviewed By: DurhamG

Differential Revision: D9236656

fbshipit-source-id: d05ec2ed2b2314ef7608c54df4f1653ca8b1b53d
2018-08-18 10:51:57 -07:00
..
__init__.py hgext: use in-core revive API 2018-08-18 10:51:57 -07:00
bundleparts.py codemod: join the auto-formatter party for commitcloud and intinitepush 2018-05-29 11:20:56 -07:00
common.py codemod: join the auto-formatter party for commitcloud and intinitepush 2018-05-29 11:20:56 -07:00
fileindexapi.py infinitepush: make listbookmarks work on Windows servers 2018-06-20 11:05:38 -07:00
indexapi.py codemod: join the auto-formatter party for commitcloud and intinitepush 2018-05-29 11:20:56 -07:00
infinitepushcommands.py infinitepush: split backups into infinitepushbackup extension 2018-06-05 04:36:06 -07:00
README infinitepush: move infinitepush from fb-hgext to hgext 2018-01-10 08:10:27 -08:00
sqlindexapi.py infinitepush: increase wait timeout 2018-07-27 04:19:19 -07:00
store.py Upgrade to 18.5b1 2018-05-30 02:23:58 -07:00

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