-
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
Remove references to Gitpod #1173
Comments
Makes sense! |
Our Gitpod config no longer works. Example error messages are: We're now using Github Codespaces to fulfil the same need, which we have documented here: We should expunge all references to Gitpod from the docs and, where appropriate, replace them with references to Codespaces. Related threads: |
Our configuration has gone stale and this no longer works. See: opensafely/documentation#1173
Our configuration has gone stale and this no longer works. See: opensafely/documentation#1173
Relatedly, I'd add that:
Footnotes
|
This landed on the pipeline board, but we're pretty sure it's a data team task, do shout if we've misunderstood something! |
This came up again today: https://bennettoxford.slack.com/archives/C63UXGB8E/p1700731771623999?thread_ts=1698849577.197769&cid=C63UXGB8E so I think it should be a reasonable priority in the near future. |
Update: we now want to remove Gitpod entirely.
@brianmackenna pointed out that the getting started guide in the docs implies that gitpod is the preferred method of running OpenSAFELY. It currently is not - at least not for committed users. If we continue to support gitpod we may want to consider:
The text was updated successfully, but these errors were encountered: