sapling/infinitepush
Stanislau Hlebik 8bdaa46014 infinitepush: set scratch bookmark locally during push
Summary:
Previously `--to` bookmark was not set locally.
This diff fixes it by setting this bookmark to the head after push happened.
This is correct because it's guaranteed that we'll push only one head.

Test Plan: Run `test-infinitepush-bundlestore.t`

Reviewers: durham, rmcelroy, mitrandir

Subscribers: mjpieters

Differential Revision: https://phabricator.intern.facebook.com/D4001168

Tasks: 12479677
2016-10-13 00:11:56 -07:00
..
integrationtests infinitepush: move integration test to the rool level directory 2016-08-31 01:44:59 -07:00
tests infinitepush: lint fixes 2016-08-26 08:01:30 -07:00
__init__.py infinitepush: set scratch bookmark locally during push 2016-10-13 00:11:56 -07:00
indexapi.py infinitepush: use addbookmarkandbundle 2016-10-12 02:59:23 -07:00
README infinitepush: sample implementation 2016-08-26 06:09:01 -07:00
store.py infinitepush: external bundle store 2016-09-07 05:20:43 -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