RunCloud Deployment Script vs Laravel Forge - why git merge instead of git pull?
Laravel Forge deployment script is obvious for me:
cd /home/forge/foo.bar
git pull origin develop
It pulls from the branch and deploys the rest.
However RunCloud says something different:
You don't have to run git fetch command but you must include your own
git merge command.
Why git merge
? Why I must? What does this mean?
Why I can't do the same as with Forge?
Can I get any human explanation?
git laravel
add a comment |
Laravel Forge deployment script is obvious for me:
cd /home/forge/foo.bar
git pull origin develop
It pulls from the branch and deploys the rest.
However RunCloud says something different:
You don't have to run git fetch command but you must include your own
git merge command.
Why git merge
? Why I must? What does this mean?
Why I can't do the same as with Forge?
Can I get any human explanation?
git laravel
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 '18 at 5:40
It's not a question about which one is better - it's a question about why the approach is different -git merge
vsgit pull origin develop
…
– Matt
Nov 20 '18 at 5:46
add a comment |
Laravel Forge deployment script is obvious for me:
cd /home/forge/foo.bar
git pull origin develop
It pulls from the branch and deploys the rest.
However RunCloud says something different:
You don't have to run git fetch command but you must include your own
git merge command.
Why git merge
? Why I must? What does this mean?
Why I can't do the same as with Forge?
Can I get any human explanation?
git laravel
Laravel Forge deployment script is obvious for me:
cd /home/forge/foo.bar
git pull origin develop
It pulls from the branch and deploys the rest.
However RunCloud says something different:
You don't have to run git fetch command but you must include your own
git merge command.
Why git merge
? Why I must? What does this mean?
Why I can't do the same as with Forge?
Can I get any human explanation?
git laravel
git laravel
asked Nov 20 '18 at 5:37


MattMatt
2,10221843
2,10221843
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 '18 at 5:40
It's not a question about which one is better - it's a question about why the approach is different -git merge
vsgit pull origin develop
…
– Matt
Nov 20 '18 at 5:46
add a comment |
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 '18 at 5:40
It's not a question about which one is better - it's a question about why the approach is different -git merge
vsgit pull origin develop
…
– Matt
Nov 20 '18 at 5:46
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 '18 at 5:40
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 '18 at 5:40
It's not a question about which one is better - it's a question about why the approach is different -
git merge
vs git pull origin develop
…– Matt
Nov 20 '18 at 5:46
It's not a question about which one is better - it's a question about why the approach is different -
git merge
vs git pull origin develop
…– Matt
Nov 20 '18 at 5:46
add a comment |
1 Answer
1
active
oldest
votes
Considering git pull
is git fetch
+ git merge
, it is probable that RunCloud does the fetch for you.
All you need is to do the merge part of the pull in order to complete it.
You can see an example in the RunCloud blog post "Laravel With GIT Deployment The Right Way"
Check out the Git part of the runcloud doc:
One of the best features of RunCloud is that you can use GIT to attach your project to your Web Application. You can do an automatic pull to sync your website with your code.
So the fetch is done for you.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53386849%2fruncloud-deployment-script-vs-laravel-forge-why-git-merge-instead-of-git-pull%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Considering git pull
is git fetch
+ git merge
, it is probable that RunCloud does the fetch for you.
All you need is to do the merge part of the pull in order to complete it.
You can see an example in the RunCloud blog post "Laravel With GIT Deployment The Right Way"
Check out the Git part of the runcloud doc:
One of the best features of RunCloud is that you can use GIT to attach your project to your Web Application. You can do an automatic pull to sync your website with your code.
So the fetch is done for you.
add a comment |
Considering git pull
is git fetch
+ git merge
, it is probable that RunCloud does the fetch for you.
All you need is to do the merge part of the pull in order to complete it.
You can see an example in the RunCloud blog post "Laravel With GIT Deployment The Right Way"
Check out the Git part of the runcloud doc:
One of the best features of RunCloud is that you can use GIT to attach your project to your Web Application. You can do an automatic pull to sync your website with your code.
So the fetch is done for you.
add a comment |
Considering git pull
is git fetch
+ git merge
, it is probable that RunCloud does the fetch for you.
All you need is to do the merge part of the pull in order to complete it.
You can see an example in the RunCloud blog post "Laravel With GIT Deployment The Right Way"
Check out the Git part of the runcloud doc:
One of the best features of RunCloud is that you can use GIT to attach your project to your Web Application. You can do an automatic pull to sync your website with your code.
So the fetch is done for you.
Considering git pull
is git fetch
+ git merge
, it is probable that RunCloud does the fetch for you.
All you need is to do the merge part of the pull in order to complete it.
You can see an example in the RunCloud blog post "Laravel With GIT Deployment The Right Way"
Check out the Git part of the runcloud doc:
One of the best features of RunCloud is that you can use GIT to attach your project to your Web Application. You can do an automatic pull to sync your website with your code.
So the fetch is done for you.
answered Nov 20 '18 at 5:40
VonCVonC
834k29026293171
834k29026293171
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53386849%2fruncloud-deployment-script-vs-laravel-forge-why-git-merge-instead-of-git-pull%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 '18 at 5:40
It's not a question about which one is better - it's a question about why the approach is different -
git merge
vsgit pull origin develop
…– Matt
Nov 20 '18 at 5:46