Changes to steps for publishing GitHub User Page #6095
Conversation
Remove the the step for switching to gh-pages branch as it is no longer a viable option.
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed. If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
|
Can I know if there are any updates to this PR? I got to know several of my friends apparently were experiencing the same issue following the existing documentation. Thanks. |
|
Do you mind merging/rebasing master to get the Travis build to pass? |
|
Sorry to bother but may I know is there anything holding up that I could be of help? It has successfully passed the Travis build. |
|
It's in now. Thanks! |
Action taken:
Update to Documentation. Removed the the step for switching to 'gh-pages' branch as it is no longer a viable option.
Reason:
As per stated on GitHub, Pages for User and Organisation could only be published from 'master' branch. The option to switch to another branch is no longer a viable option.
Extract from GitHub:
"If your site is a User or Organization Page that has a repository named .github.io or .github.io , you cannot publish your site's source files from different locations. User and Organization Pages that have this type of repository name are only published from the master branch."
GitHub reference:
https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/
Note:
In the case of a user's page, users only need to do the second step, instead of two.
"Additionally, tweak your package.json scripts to push deployments to master" solely would suffice as per tested on my own Github User Page. (StevenTan.GitHub.io)
Thanks,
Steven