8000 Changing cookbook/ deployment info by poznet · Pull Request #3965 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

Changing cookbook/ deployment info #3965

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 21 commits into from
Closed

Conversation

poznet
Copy link
@poznet poznet commented Jun 21, 2014
Q A
Doc fix? yes
New docs? no
Applies to all
Fixed tickets

Added info in cookbook in deployment about checking server requirements php app/check.php

@@ -36,6 +36,8 @@ There are several ways you can deploy a Symfony2 application.

Start with a few basic deployment strategies and build up from there.



Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove these blank lines.

@xabbuh
Copy link
Member
xabbuh commented Jun 22, 2014

The lowercased headlines were not introduced by you. But it would great if you'd change them too.

@poznet
Copy link
Author
poznet commented Jun 22, 2014

Done.

@xabbuh
Copy link
Member
xabbuh commented Jun 23, 2014

@j00seph Could you please also rebase your branch?

@wouterj
Copy link
Member
wouterj commented Jun 23, 2014

@xabbuh it doesn't have conflicts

@xabbuh
Copy link
Member
xabbuh commented Jun 23, 2014

@wouterj No, but at least for me GitHub fails to display the file diff. I hoped that rebasing would solve that issue.

@wouterj
Copy link
Member
wouterj commented Jun 23, 2014

@xabbuh I don't have that issue

@poznet
Copy link
Author
poznet commented Jun 23, 2014

@xabbuh - are you sure that this problem isn't on your side ? (i don't know - browser cache etc. ) ?

ok
@xabbuh
Copy link
Member
xabbuh commented Jun 23, 2014

@j00seph Seems so to be. Though all other pull requests work as expected. Nevertheless, I managed to have a look at the diff using another browser. Looks good so far.

@weaverryan
Copy link
Member

@j00seph Can you try rebasing again (or maybe open a fresh PR)? GitHub shows a lot of extra commits, which might not be a problem, but more strangely, when I try to merge, it says that you've made changes to cookbook/deployment-tools.rst (the actual path, and the one that's shown in GitHub is cookbook/deployment/tools.rst).

Thanks!

@poznet
Copy link
Author
poznet commented Jul 1, 2014

rebased - try now

@@ -1 +1 @@
Subproject commit 03bc1c60172a280619e3476f22b111b4a187895d
Subproject commit 74553741a70af2b862de77e1de12fb2f74ff33a4
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this change doesn't look right

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there is a rebase problem again

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is probably because the submodule was not updated locally to match the version used in master, and git add . was used when resolving conflicts during the rebase, adding the submodule target change to the diff

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm, actually, the rebase is totally messy: the upstream commits have been rebased instead of rebasing the branch on top of upstream commits. Look at the list of commits in the PR. This is why this appears in the diff

@wouterj
Copy link
Member
wouterj commented Jul 1, 2014

@j00seph could you please execute the following commands: (I assume "origin" remote refers to this repo and "j00seph" remote refers to your fork)

# fetch origin
$ git fetch origin
# make a new branch containing your changes
$ git checkout -b checking-server-requirements
# rebase your new branch to be based on 2.3 instead of your master
$ git rebase --onto master origin/2.3
# ... resolve conflicts
# push the new branch to your fork
$ git push j00seph checking-server-requirements

After this, create a new PR for the "checking-server-requirements" branch to symfony:2.3

@stof
Copy link
Member
stof commented Jul 1, 2014

@wouterj the right command to base the branch on 2.3 is git rebase --onto origin/2.3 master, not the opposite

@weaverryan
Copy link
Member

@j00seph Can you follow Wouter's directions (except change the rebase command to look like Stof's recommendation)?

What I'm ultimately looking for is to see just your commits under the Commits tab :).

Thanks!

@poznet
Copy link
Author
poznet commented Jul 2, 2014

give me day or two , i'm out of time at this moment :)

@wouterj wouterj mentioned this pull request Aug 15, 2014
@wouterj
Copy link
Member
wouterj commented Aug 15, 2014

I did the rebasing for you in #4124 Thanks for submitting your changes to the Symfony repo!

@wouterj wouterj closed this Aug 15, 2014
weaverryan added a commit that referenced this pull request Aug 16, 2014
This PR was merged into the 2.3 branch.

Discussion
----------

Rebased #3965

Rebased version of @j00seph's PR: #3965

Commits
-------

d8dc7aa some minor improvements
70b7d41 Update deployment-tools.rst
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants
0