-
Notifications
You must be signed in to change notification settings - Fork 208
Issues/3466 Move away from Gitpod #3569
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
base: dev
Are you sure you want to change the base?
Conversation
…tools into issues/3466-gitpod
…r. Update postCreateCommand to match context
Note: This still uses (a newer) gitpod base image and thus also the |
Codecov ReportAll modified and coverable lines are covered by tests ✅
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…ion to handle auth
Ready for review, if you have the time @mashehu @mahesh-panchal ! 🎉 Summary of latest changes:
Failing TestTo make the failing test work, I assume something in template_features.yml needs to be changed? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also need to these files to the files_changed lint tests. And remove the gitpod.yml file
# copy this repo at current revision | ||
COPY . /root/nfcore-tools/ | ||
|
||
# install python 3.11, local nf-core tools version, and precommit hooks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why python 3.11 specifically? The minimal version is 3.9 currently.
|
||
"features": { | ||
"ghcr.io/devcontainers/features/docker-outside-of-docker:1": { | ||
"version": "latest" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pin this to a specific version please. Renovate will help us update it.
}, | ||
|
||
// Add the IDs of extensions you want installed when the container is created. | ||
"extensions": ["ms-python.python", "ms-python.vscode-pylance", "nf-core.nf-core-extensionpack"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add ruff here as well.
nextflow self-update | ||
|
||
# Update welcome message | ||
echo "Welcome to the nf-core/tools devcontainer!" > /usr/local/etc/vscode-dev-containers/first-run-notice.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
echo "Welcome to the nf-core/tools devcontainer!" > /usr/local/etc/vscode-dev-containers/first-run-notice.txt | |
echo "Welcome to the nf-core devcontainer!" > /usr/local/etc/vscode-dev-containers/first-run-notice.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we symlink files that are the same? So we save the hassle of keeping everything in sync?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reducing redundancy sounds good, but I would rather not have symlinks in the template, to make things more simple. If we add them, let's remember to use followlinks?True
in Jinja2.
#!/usr/bin/env bash | ||
|
||
# Update welcome message | ||
echo "Welcome to the nf-core pipeline devcontainer!" > /usr/local/etc/vscode-dev-containers/first-run-notice.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use jinja variables to customize the welcome message to the current pipeline.
The new template file |
"version": "21.0.6-ms" | ||
}, | ||
"ghcr.io/rocker-org/devcontainer-features/miniforge:2": { | ||
"version": "latest" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the version should also be pinned here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reducing redundancy sounds good, but I would rather not have symlinks in the template, to make things more simple. If we add them, let's remember to use followlinks?True
in Jinja2.
Description
Addresses the suggestions in issue 3466 to move away from gitpod and towards devcontainer for Github codespaces.
PR checklist
CHANGELOG.md
is updateddocs
is updated