Skip to content

docs: add community health files (CONTRIBUTING, COC, issue templates)#8

Merged
Co-Messi merged 1 commit into
mainfrom
docs/community-health
Jun 15, 2026
Merged

docs: add community health files (CONTRIBUTING, COC, issue templates)#8
Co-Messi merged 1 commit into
mainfrom
docs/community-health

Conversation

@Co-Messi

Copy link
Copy Markdown
Owner

Salvages the genuinely useful community-health files from the old wip-branding branch (the rest was exploratory banner art, dropped):

  • CONTRIBUTING.md — local setup, good-first-tasks, PR checklist, project principles
  • CODE_OF_CONDUCT.md — short, plain
  • .github/ISSUE_TEMPLATE/ — bug_report, feature_request, demo_request

Completes GitHub's Community Standards checklist. Docs-only, no code.

Salvaged from the wip-branding working branch before retiring it: a focused
CONTRIBUTING guide tied to the project principles, a short Code of Conduct,
and bug/feature/demo issue templates. Fills out GitHub's Community Standards.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 989349e918

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread CONTRIBUTING.md
```bash
npm install
npm run build
npm run test

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Document E2E prerequisites before running tests

In a fresh checkout this setup stops at npm run test: package.json maps that to vitest run, so it also runs the E2E specs (test/record.e2e.test.ts and test/generate.e2e.test.ts) that require Chromium plus ffmpeg/ffprobe, and the README already calls out those prerequisites for npm run test:e2e. Please either use the fast test target here or add the Playwright/ffmpeg setup step before asking new contributors to run the full suite.

Useful? React with 👍 / 👎.

@Co-Messi Co-Messi merged commit 2d6e4dd into main Jun 15, 2026
2 checks passed
@Co-Messi Co-Messi deleted the docs/community-health branch June 15, 2026 01:54
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.

1 participant