manekinekko / manekinekko/awesome-devcontainers
IDEs
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 513
- Forks
- 31
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 5
Description
IDEs
Emacs
IntelliJ
NeoVim
- https://github.com/esensar/nvim-dev-container
- https://github.com/jamestthompson3/nvim-remote-containers
Vim
Visual Studio
VScode
- https://github.com/Microsoft/vscode-remote-release
- https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers
## IDEs
- https://containers.dev/supporting#editors
### Emacs
- https://github.com/johannes-mueller/devcontainer.el
### IntelliJ
### NeoVim
- https://github.com/esensar/nvim-dev-container
- https://github.com/jamestthompson3/nvim-remote-containers
### Vim
- https://github.com/mikoto2000/devcontainer.vim
### Visual Studio
### VScode
- https://github.com/Microsoft/vscode-remote-release
- https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides an IDE list and links but names no repository file or test. Start by locating the existing IDE section in this curated list and compare it with containers.dev/supporting#editors and the linked integrations. Done means the section is non-duplicated and accurately covers the intended editor links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- emacs, neovim, vim, vscode
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100