RunCloud Deployment Script vs Laravel Forge - why git merge instead of git pull?
up vote
1
down vote
favorite
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
asked Nov 20 at 5:37
Matt
2,05321843
add a comment |
up vote
1
down vote
favorite
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
asked Nov 20 at 5:37
Matt
2,05321843
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 at 5:40
It's not a question about which one is better - it's a question about why the approach is different -git mergevsgit pull origin develop…
– Matt
Nov 20 at 5:46
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
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
asked Nov 20 at 5:37
Matt
2,05321843
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 at 5:37
Matt
2,05321843
asked Nov 20 at 5:37
Matt
2,05321843
asked Nov 20 at 5:37
Matt
2,05321843
asked Nov 20 at 5:37
Matt
2,05321843
asked Nov 20 at 5:37
Matt
2,05321843
2,05321843
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 at 5:40
It's not a question about which one is better - it's a question about why the approach is different -git mergevsgit pull origin develop…
– Matt
Nov 20 at 5:46
add a comment |
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 at 5:40
It's not a question about which one is better - it's a question about why the approach is different -git mergevsgit pull origin develop…
– Matt
Nov 20 at 5:46
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 at 5:40
This is apples to oranges to me. I don't follow the comparison.
– Tim Biegeleisen
Nov 20 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 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 at 5:46
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
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 at 5:40
VonC
825k28425933126
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
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 at 5:40
VonC
825k28425933126
add a comment |
up vote
0
down vote
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 at 5:40
VonC
825k28425933126
add a comment |
up vote
0
down vote
up vote
0
down vote
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 at 5:40
VonC
825k28425933126
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 at 5:40
VonC
825k28425933126
answered Nov 20 at 5:40
VonC
825k28425933126
answered Nov 20 at 5:40
VonC
825k28425933126
answered Nov 20 at 5:40
VonC
825k28425933126
825k28425933126
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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 at 5:40
It's not a question about which one is better - it's a question about why the approach is different -
git mergevsgit pull origin develop…– Matt
Nov 20 at 5:46