Auto deploy changes from `devcontainers/spec` to containers.dev

Open
#25 2 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
devops, release

Research direction

Start by tracing how changes move from devcontainers/spec to containers.dev and documenting the existing 1:1 copy process and formatting tweaks. Done means spec changes are deployed automatically to containers.dev with the required formatting preserved.

Written by the indexing model from the issue text.

Description

enhancement

It would be great to automate the deployment of spec changes. Right now we do a 1:1 copy with minor formatting tweaks - so it shouldn't be too hard.

Dominant language
HTML
Stars
207
Forks
435
Avg merge
1d 17h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devcontainers/devcontainers.github.io

All issues in devcontainers/devcontainers.github.io

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.