Skip to content

docs: community files and repo hygiene - #1

Open
DroBov1Tya wants to merge 2 commits into
mainfrom
community-files
Open

DroBov1Tya wants to merge 2 commits into
mainfrom
community-files

Conversation

@DroBov1Tya

Copy link
Copy Markdown
Owner

Adds what a newcomer looks for first: a code of conduct (Contributor Covenant 2.1), issue forms for bugs and ideas (blank issues off, security reports go to private advisories), a first-change path and a skill-writing pointer in CONTRIBUTING.

Also ignores .playwright-mcp/, names only the public working note in the README, and drops docs/screenshots/quiz.gif (6.4 MB, linked from nowhere).

Not verified: the issue forms against GitHub's schema (they parse as YAML); they show once merged.

A public repository needs a Code of Conduct, issue forms that ask for the
version, system and client, and a clear path for a first change and for a
skill. Also ignore the Playwright MCP scratch folder.
docs/todo.md and docs/gui-todo.md are ignored and never reach the repository, so
the README names only structure-audit.md. quiz.gif (6.4 MB) is linked from
nowhere; the blob stays in history, new clones stop checking it out.

This branch has not been deployed

No deployments
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