Open cacieprins opened 5 months ago
I also discovered that running
yarn workspace @packages/example deploy
from a fork deploys to the fork's gh-pages
branch. The web's structure is however not set up to run correctly from a fork, Only the index.html
displays correctly. Navigation to other pages does not work and CSS formatting does not work on other pages either.
That may become irrelevant if the deploy process is changed. If not it should be noted in the README.
Possibly something like Percy could be used for visual comparison of pending changes to https://example.cypress.io ?
example.cypress.io
website to be tested before it is moved to production
Current behavior:
@packages/example
deploys directly to production example.cypress.io as soon as the deploy command executes, via thegh-pages
tool.As a stopgap to prevent outages:
gh-pages
should be a protected branchdeploy
command in@packages/example
should open a pull request togh-pages
instead of committing directlyIn the future:
cypress-example-kitchensink
should deploy continuously to a staging environmentcypress-example-kitchensink
toexample.cypress.io
are handled via circleci in thecypress-example-kitchensink
repository, triggered by creating a github release as a part of thecypress
deploy processcypress
ci, once thecypress
release process is automated