Build and test the devcontainer in CI
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 67/100
Research direction
Read the existing workflow files and .devcontainer/devcontainer.json, then check the repository’s path-filter and scheduled workflow conventions. Add a SHA-pinned devcontainers/ci job that builds the devcontainer and runs make test and ./subenum -simulate example.com inside it; done when CI runs those checks on relevant changes and weekly.
Written by the indexing model from the issue text.
Description
Why it matters
The README's "Open in Codespaces" badge and the Labs page tell students and new contributors that the devcontainer gives them a working make test and ./subenum. Nothing checks that, so a broken image tag or postCreateCommand would only show up when someone opens a Codespace.
Evidence
.devcontainer/devcontainer.json(#75) usesmcr.microsoft.com/devcontainers/go:1.26-bookworm, and itspostCreateCommandinstalls golangci-lint v2.14.0 and builds the binary.- When it was added, only the image tag's existence and the commands themselves (run on Windows) were checked. Docker was not available, so the container was never built.
- CI builds the release Dockerfile but not the devcontainer.
Suggested approach
Add a CI job (path-filtered to .devcontainer/**, plus a weekly schedule) using devcontainers/ci. It should build the container and run make test and ./subenum -simulate example.com inside it. Pin the action by SHA, like the other workflows.
Done when
A CI job builds the devcontainer and runs the test suite and a simulate scan inside it.
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 3
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 TMHSDigital/subenum
-
area: cli enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
TMHSDigital/subenum#136 ·
Maintainers usually reply within 1 day
-
community documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TMHSDigital/subenum#135 ·
Maintainers usually reply within 1 day
-
area: dns enhancement good first issue
Difficulty 2/5 Under an hour Newbie friendliness 90/100
TMHSDigital/subenum#134 ·
Maintainers usually reply within 1 day
-
community marketing priority: low
Difficulty 5/5 Over a week Newbie friendliness 35/100
TMHSDigital/subenum#132 · 1 comment ·
Maintainers usually reply within 1 day
-
feature priority: low
Difficulty 5/5 Over a week Newbie friendliness 35/100
TMHSDigital/subenum#131 ·
Maintainers usually reply within 1 day
All issues in TMHSDigital/subenum
Similar issues
-
L: github:actions L: php:composer
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
dependabot/dependabot-core#16493 ·
Maintainers usually reply within 1 day
-
Controller pods on default limits CrashLoopBackOff and constantly reclaim memoryPossibly taken @brsmnv claimed this today. Openbug
Difficulty 2/5 Under an hour Newbie friendliness 68/100
ironcore-dev/ironcore-net#560 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mark3labs/mcp-go#1039 · 1 comment ·
Maintainers usually reply within 8 days
-
enhancement
Difficulty 2/5 Under an hour Newbie friendliness 78/100
JuliusBrussee/caveman#1214 ·
Maintainers usually reply within 1 day
-
domain/core domain/mail enhancement
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day