-
Notifications
You must be signed in to change notification settings - Fork 9
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
consider adding gitpod or codespaces #59
Comments
I think the same way codespaces get setup also allows for using vscode devcontainers which can be a nice addition as well |
Has anyone set this up for their project? I'd be interested in checking it out. |
Once again, I just know this from the nf-core project. E.g. https://gitpod.io/#https://github.com/nf-core/rnaseq I haven't really used it myself, but what I can tell from slack the experience is mostly positive so far, especially for new developers. |
Is this something that could be added later or opt in? I think this can make sense for some projects, especially larger ones like the core-tools. But not all, and it's an extra thing to maintain. My concern is that it's an extra thing to maintain, and I would expect the image setup would break before most projects get a contributor. Especially if the current devs aren't using it. |
Setting up github codespaces or gitpod is a nice way of getting contributors started more quickly.
It essentially starts a virtual machine somewhere with a containerized workspace with all dev dependencies (pre-commit etc) readily installed. This VM serves a vscode web version, or can be connected to vscode desktop.
The text was updated successfully, but these errors were encountered: