You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue and PR templates do two jobs here: they get us the information we need, and they teach the project's standards at the moment someone is about to submit.
Acceptance
.github/ISSUE_TEMPLATE/bug_report.yml — version (keel --version, which stamps commit and build kind), paper or live, the rail or rule involved, what was expected
.github/ISSUE_TEMPLATE/feature_request.yml
.github/ISSUE_TEMPLATE/compliance_question.yml — a distinct route for "should this asset/mechanism be classified differently", which is not a bug and must not be triaged as one
.github/ISSUE_TEMPLATE/config.yml pointing security reports at SECURITY.md, not at a public issue
.github/PULL_REQUEST_TEMPLATE.md — gates passed, tests-first evidence, and a checkbox for "this touches a rail or a default classification" so those get the review they need
Issue and PR templates do two jobs here: they get us the information we need, and they teach the project's standards at the moment someone is about to submit.
Acceptance
.github/ISSUE_TEMPLATE/bug_report.yml— version (keel --version, which stamps commit and build kind), paper or live, the rail or rule involved, what was expected.github/ISSUE_TEMPLATE/feature_request.yml.github/ISSUE_TEMPLATE/compliance_question.yml— a distinct route for "should this asset/mechanism be classified differently", which is not a bug and must not be triaged as one.github/ISSUE_TEMPLATE/config.ymlpointing security reports atSECURITY.md, not at a public issue.github/PULL_REQUEST_TEMPLATE.md— gates passed, tests-first evidence, and a checkbox for "this touches a rail or a default classification" so those get the review they need