Instead of relying on the client to manage its own merge data in firestore, the clio-store backend should provide a custom endpoint for storing merges (and it should be consistent with the pull request API). The endpoint should appropriately handle the new versioning concepts as defined in #4.
Instead of relying on the client to manage its own merge data in firestore, the
clio-storebackend should provide a custom endpoint for storing merges (and it should be consistent with the pull request API). The endpoint should appropriately handle the new versioning concepts as defined in #4.cc @DocSavage @tingzhao @hubbardp @umayaml