Skip to content

Clarify that Remote Containers Clone Repository commands are not supported #4199

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.

Sign up for GitHub

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

Merged
jurre merged 1 commit into from
Oct 8, 2021
Merged

Clarify that Remote Containers Clone Repository commands are not supported #4199

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,11 @@ Once that's finished, start the `Debug Dry Run` configuration `(F5)` and you'll
to select a package manager and a repository to perform a dry run on.
Feel free to place breakpoints on the code.

⚠️ The `Clone Repository ...` commands of the Remote Containers extension are currently
missing some functionality and are therefore not supported. You have to clone the
repository manually and use the `Reopen in Container` or `Open Folder in Container...`
command.

## Releasing

Triggering the jobs that will push the new gems is done by following the steps below.
Expand Down