Merged
Conversation
Three structured surfaces for outside contributors: - CONTRIBUTING.md — short guide. Dev setup link to README, branch conventions, what we expect in PRs (tests for new logic, no new runtime deps without reason, no analytics/trackers, strict CSP), no-style-config-yet caveat, and the implicit MIT licensing. - .github/ISSUE_TEMPLATE/bug_report.yml — GitHub form with fields for the bug, an optional zone snippet (rendered as plain-text so it preserves whitespace), expected behavior, where it happens, browser, and console errors. - .github/ISSUE_TEMPLATE/feature_request.yml — form steered to "what problem" first, then proposed solution, with a dropdown asking whether the idea fits the self-operating philosophy. - .github/ISSUE_TEMPLATE/config.yml — disables blank issues; routes questions to Discussions and security reports to GitHub Security Advisories. - .github/PULL_REQUEST_TEMPLATE.md — Summary + Test plan + Screenshots sections plus a checklist mirroring the CONTRIBUTING expectations. No code changes; all four files pure scaffolding for the GitHub UI. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
crhaglun
pushed a commit
that referenced
this pull request
May 8, 2026
Three structured surfaces for outside contributors: - CONTRIBUTING.md — short guide. Dev setup link to README, branch conventions, what we expect in PRs (tests for new logic, no new runtime deps without reason, no analytics/trackers, strict CSP), no-style-config-yet caveat, and the implicit MIT licensing. - .github/ISSUE_TEMPLATE/bug_report.yml — GitHub form with fields for the bug, an optional zone snippet (rendered as plain-text so it preserves whitespace), expected behavior, where it happens, browser, and console errors. - .github/ISSUE_TEMPLATE/feature_request.yml — form steered to "what problem" first, then proposed solution, with a dropdown asking whether the idea fits the self-operating philosophy. - .github/ISSUE_TEMPLATE/config.yml — disables blank issues; routes questions to Discussions and security reports to GitHub Security Advisories. - .github/PULL_REQUEST_TEMPLATE.md — Summary + Test plan + Screenshots sections plus a checklist mirroring the CONTRIBUTING expectations. No code changes; all four files pure scaffolding for the GitHub UI. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Scaffolds GitHub's contribution surfaces:
Test plan
Notes
No code changes. The Discussions link in config.yml assumes Discussions is enabled on the repo — if it's not, GitHub will quietly skip that contact link until it is.
🤖 Generated with Claude Code