Merging branches #677
Description
I'm implementing a solution where a team can drop import files in a GCS bucket and start the import process. Currently I'm creating a separate branch for each import, so teams can test whether or not the import worked, before they switch over.
I'm wondering how the merge process works and how I can get rid of these import branches.
Initially I thought it was sufficient to execute a POST request to /merges, but that doesn't seem to work:
Status: 500
Body: {
"error" : "INTERNAL_SERVER_ERROR",
"message" : "No static resource merges."
}
I'm wondering what the exact process is to do this. I can see that you also can pass in a reviewId. Initially I thought I had to create a review by posting a request to /reviews, but that doesn't work either:
Status: 400
Body: {
"error" : "BAD_REQUEST",
"message" : "A merge review should only be used during rebase, not promotion."
}
Any help would be appreciated. Thanks!