Question / Improvement: Incremental publishing of devcontainer features and `devcontainer-collection.json`
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- cli
Research direction
No files, tests, or entry points are named. Start by reproducing incremental and all-at-once feature publishing, then trace how devcontainer-collection.json is generated; define whether incremental publishing is supported, how entries should be merged, or what documentation should state.
Written by the indexing model from the issue text.
Description
Description
We’re exploring whether the Dev Container CLI is intended to support publishing devcontainer features one by one.
When features are published individually, devcontainer-collection.json is regenerated each time and ends up containing only the last published feature. When all features are published together, the collection file is generated correctly.
This behavior seems consistent and intentional, so this is not a bug report, more a question and possible improvement discussion.
Question / Improvement Idea
Is publishing features incrementally an intended workflow?
If this use case is in scope, would it make sense to support:
- Merging newly published features into an existing
devcontainer-collection.json, or - A flag or documented approach for incremental publishing?
The motivation is mainly CI/CD robustness, where publishing one feature should not block others.
If incremental publishing is intentionally unsupported, clarification or documentation around this would also be very helpful.
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 461
- Avg merge
- 18m
- Merged PRs (30d)
- 5
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.
More from devcontainers/cli
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
devcontainers/cli#1203 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
devcontainers/cli#1178 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
devcontainers/cli#1308 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
devcontainers/cli#1307 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
devcontainers/cli#1305 ·
All issues in devcontainers/cli
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100