chore: per-type issue intake forms + config#8
Merged
Conversation
Five issue forms (feature/bug/chore/spike/docs) — each pre-sets its issue type and carries Acceptance Criteria + a Definition-of-Done checklist — plus config.yml (blank issues off; ideas routed to org Discussions). Canonical in template; ready for sync_scaffold to propagate org-wide. Co-Authored-By: Claude Opus 4.8 <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.
Closes #7.
Adds the per-type issue intake forms to
.github/ISSUE_TEMPLATE/:feature·bug·chore·spike·docs— each pre-sets its issuetype:and carries Acceptance Criteria + a Definition-of-Done checkbox block — plusconfig.yml(blank_issues_enabled: false; ideas → org Discussions).Why: structured intake so every issue is born well-formed (Definition-of-Ready prompts + the always-present DoD checklist) — part of making the org self-describing. Canonical here in
template;sync_scaffoldpropagates to every repo.How verified: YAML structure reviewed; the five forms map 1:1 to the org issue types; the Discussions URL resolves (org Discussions enabled, source
norikit/norikit).Part of the Org framework foundations epic (#12).
🤖 Generated with Claude Code