Skip to content

Commit 51c742e

Browse files
Remove PR previews for now (#1595)
Part of #1043. Code Engine is shut down tomorrow, so we need to turn off previews for now. We're still working on what the replacement is. Once that's ready, we'll revive whichever of these files are relevant.
1 parent 281468c commit 51c742e

File tree

7 files changed

+0
-325
lines changed

7 files changed

+0
-325
lines changed

.github/actions/set-up-ibm-cloud/action.yml

Lines changed: 0 additions & 70 deletions
This file was deleted.

.github/workflows/deploy-code-engine.yml

Lines changed: 0 additions & 91 deletions
This file was deleted.

.github/workflows/preview-docs-teardown.yml

Lines changed: 0 additions & 50 deletions
This file was deleted.

.github/workflows/preview-docs.yml

Lines changed: 0 additions & 38 deletions
This file was deleted.

.github/workflows/staging.yml

Lines changed: 0 additions & 33 deletions
This file was deleted.

Dockerfile

Lines changed: 0 additions & 31 deletions
This file was deleted.

README.md

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -89,18 +89,6 @@ API docs authors can preview their changes to one of the APIs by using the `-a`
8989
1. Run `npm run gen-api -- -p <pkg-name> -v <version> -a <path/to/docs/_build/html>`.
9090
2. Execute `./start` and open up `http://localhost:3000`, as explained in the prior section.
9191

92-
## Preview the docs in PRs
93-
94-
Contributors with write access to this repository can use live previews of the docs: GitHub will deploy a website using your changes.
95-
96-
To use live previews, push your branch to `upstream` rather than your fork. GitHub will leave a comment with the link to the site. Please prefix your branch name with your initials, e.g. `EA/fix-build-typo`, for good Git hygiene.
97-
98-
## Staging
99-
100-
We also re-deploy the docs every time we merge into `main` at the site https://qiskit-docs-preview-staging.1799mxdls7qz.us-south.codeengine.appdomain.cloud.
101-
102-
This staging environment can be useful to see how the docs are rendering before we push it live to production.
103-
10492
## Execute notebooks
10593

10694
Before submitting a new notebook or code changes to a notebook, you must run

0 commit comments

Comments
 (0)