Skip to content

Add mattmazzola/devcontainers to collections-index.yml #569

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

Open
wants to merge 2 commits into
base: gh-pages
Choose a base branch
from

Conversation

mattmazzola
Copy link

@mattmazzola mattmazzola commented Jun 21, 2025

What type of PR is this?

  • Add a new dev container collection
  • Update to an existing dev container collection
  • Documentation/spec update
  • Other containers.dev site update (UX, layout, etc)

Related Issues

  • Related Issue #
  • Closes #

Description

Collection checklist

If your PR contributes a new collection, please utilize this checklist:

  • Collection name
  • Maintainer name
  • Maintainer contact link (i.e. link to a GitHub repo, email)
  • Repository URL
  • OCI Reference
  • I acknowledge that this collection provides new functionality, distinct from the existing collections part of this index.

@mattmazzola mattmazzola marked this pull request as ready for review June 21, 2025 23:53
@mattmazzola mattmazzola requested a review from a team as a code owner June 21, 2025 23:53
@Kaniska244
Copy link

Kaniska244 commented Jun 30, 2025

Hello @mattmazzola ,

Thank you for the contribution. One small question, does this template offer anything different from this one already listed in the devcontainers templates index.

@mattmazzola
Copy link
Author

mattmazzola commented Jul 10, 2025

does this template offer anything different

I would say yes, it comes with a lot of other features and extensions which are mostly personal preferences. For example, mine uses the UV container feature for install, while the one you liked uses RUN commands in Dockerfile to install uv.
However, it may not differ in the way that is expected or acceptable by some convention I am not aware of.

I think if the intention is to keep the index only referring to minimal set of devcontainers then perhaps this PR isn't what I thought and can be closed.

I wanted a way to make the devcontainers I was developing show in VScode for convenience and for other collaborators to use and test. Based on the documentation I found, adding my templates to the index seemed liked the only way.

Although I anticipate that this process could contribute to noise if everyone adds their personal containers to the index and it causes the index to be overwhelming and perhaps less usable. However, I assumed this is unlikely since very few people are writing container templates

I saw what looked like other personal devcontainer repositories listed in the index and thought, Ok, perhaps this practice is allowed and expected, and so I submitted mine as well

From what I understand, once your repo is added. You can add other templates and they will implicitly show up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants