-
Notifications
You must be signed in to change notification settings - Fork 7
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
Replace Gitpod with GitHub Codespaces #1398
Conversation
We are replacing any use of Gitpod with GitHub Codespaces.
This does not yet update the images.
To make it simpler.
I think a subsequent improvement would be to consolidate the GitHub Codespaces page with the Getting Started guide. There is some overlap there. We could merge in the sections that refer to creating a demonstration research repository to the Getting Started guide, or remove them entirely. But this PR at least drops the mention of Gitpod, so that could be a subsequent PR either shortly or when we revisit the Getting Started guide. |
Deploying with Cloudflare Pages
|
efd0a10
to
388ab68
Compare
388ab68
to
a01a8ad
Compare
There's a tiny bit of work here to decide:
The content changes could be reviewed now. |
It would be better to organise these per directory probably (#1400), but avoiding that for now. This at least marks more clearly what these images are for. Have not renamed the `win-anaconda-prompt.png` and `win-docker-starting.png` because the `win-docker-starting.png` is used elsewhere.
The branch is now `main`.
Remove Gitpod images and replace with GitHub Codespaces.
These are no longer used.
a01a8ad
to
ebe6b07
Compare
I'll leave the screenshots as they are. If we find cropping some of them is better, we could do that in future. |
Fixes #1173.
Our Gitpod configuration for the research template stopped working and has now been removed. Instead, we currently have a configuration that works with GitHub Codespaces.
The Getting Started guide could not be followed by users trying to use OpenSAFELY via Gitpod. This PR updates the Getting Started guide to use Codespaces.
We originally added Gitpod when Codespaces wasn't available for all. We now favour GitHub Codespaces because Codespaces doesn't require:
All this simplifies the process for users, and our explanations of that process.
We could consolidate some of the other GitHub Codespaces page with this one, as they now overlap, but that can be a future PR.