-
Notifications
You must be signed in to change notification settings - Fork 0
Validate Codespaces setup and document first-run gaps #1
Copy link
Copy link
Open
Labels
codespacesGitHub Codespaces, devcontainer, or Docker development setupGitHub Codespaces, devcontainer, or Docker development setupdocsDocumentation, examples, onboarding, or explanatory improvementsDocumentation, examples, onboarding, or explanatory improvementsgood first issueScoped entry point for new contributors.Scoped entry point for new contributors.
Description
Metadata
Metadata
Assignees
Labels
codespacesGitHub Codespaces, devcontainer, or Docker development setupGitHub Codespaces, devcontainer, or Docker development setupdocsDocumentation, examples, onboarding, or explanatory improvementsDocumentation, examples, onboarding, or explanatory improvementsgood first issueScoped entry point for new contributors.Scoped entry point for new contributors.
I added a Codespaces/devcontainer path so a new contributor can inspect this project without first setting up a custom local machine.
What would help most is a fresh run from someone who did not build the repo originally.
Suggested check
bash node scripts/enterprise-readiness-check.mjs node --test tests/enterprise-readiness.test.mjsGood outcome
A small PR that improves the first-run experience is enough. Even a precise issue comment describing what was confusing is useful.
Please do not add real secrets or provider credentials.