You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the second remote, I went in and did a git init to create an empty repo.
Now that I have listed the second remote, blt will deploy a develop-build branch to both targets. However, it is also trying to merge from both remotes at the start of the deployment procedure. Here is the output:
blt > deploy:remote:add:
[echo] Fetching from git remote user@remote1:/path/to/.git
blt > deploy:remote:pull:
remote: Counting objects: 37647, done.
remote: Compressing objects: 100% (26317/26317), done.
remote: Total 37647 (delta 11146), reused 35219 (delta 8734)
Receiving objects: 100% (37647/37647), 33.25 MiB | 31.30 MiB/s, done.
Resolving deltas: 100% (11146/11146), done.
From user@remote1:/path/to/.git
* branch develop-build -> FETCH_HEAD
* [new branch] develop-build -> 7389ba2d40309ee4e38831ab8b02e886/develop-build
Switched to a new branch 'develop-build'
blt > deploy:remote:add:
[echo] Fetching from git remote user@remote2:/path/to/.git
blt > deploy:remote:pull:
user@remote2 password:
fatal: Couldn't find remote ref develop-build
fatal: The remote end hung up unexpectedly
fatal: A branch named 'develop-build' already exists.
merge: 3ef323a363f7b15e7f6ba1b78888a87a/develop-build - not something we can merge
Is this okay? If not, is there a recommended way to deploy to more than 1 target?
The text was updated successfully, but these errors were encountered:
My system information:
Just a followup of a previous question.
On the second remote, I went in and did a
git init
to create an empty repo.Now that I have listed the second remote, blt will deploy a
develop-build
branch to both targets. However, it is also trying to merge from both remotes at the start of the deployment procedure. Here is the output:Is this okay? If not, is there a recommended way to deploy to more than 1 target?
The text was updated successfully, but these errors were encountered: