Remove GitPod config #386
Closed
Remove GitPod config #386
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Gitpod still works and is being used by @sarawilcox, @anandamaryon1 and team, so I'll close this for now. It sounds like it could be a useful tool to potentially point others to too, although we should also investigate how it compares to GitHub Codespaces and whether there’s any overlap or if one is better than the other? (I’m not super familiar with either) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitPod looks kinda interesting - a cloud-based development environment I think?
I don’t know if anyone’s still using this for this project though? And perhaps GitHub Codespaces would do the same thing, but within the NHS's existing GitHub account billing?
Suggest we remove the config and documentation from the README for now, unless anyone knows a good reason to keep it?