chore: org-wide YAML issue forms + PR template at .github/ path#6
Draft
chazmaniandinkle wants to merge 1 commit intomainfrom
Draft
chore: org-wide YAML issue forms + PR template at .github/ path#6chazmaniandinkle wants to merge 1 commit intomainfrom
chazmaniandinkle wants to merge 1 commit intomainfrom
Conversation
Per 2026-04-24 public-repo audit §OSS-readiness-gaps #4: every repo in cogos-dev is missing issue templates, and the existing markdown templates at this repo's root-level ISSUE_TEMPLATE/ directory do not surface on member repos through org-default inheritance. GitHub inherits defaults from the cogos-dev/.github repo ONLY when they live under .github/ — not at the repo root. Adding the YAML form versions at .github/ISSUE_TEMPLATE/ so every cogos-dev repo (including cogos, mod3, constellation, cog-sandbox-mcp, charts, skills, research) picks them up automatically. YAML forms over the old markdown: enforces structured fields (dropdowns + required fields) instead of free-form bodies, which cuts triage work materially. Leaving the root-level ISSUE_TEMPLATE/ and PULL_REQUEST_TEMPLATE.md in place for this repo's own local use. Also copying the PR template to .github/PULL_REQUEST_TEMPLATE.md so the same inheritance applies. config.yml adds a 'Security report' link pointing at SECURITY.md, to redirect vulnerability reports out of public issue threads.
This was referenced Apr 24, 2026
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.
What
Adds YAML issue forms at
.github/ISSUE_TEMPLATE/:bug.yml— structured bug report with project dropdown, required fieldsfeature.yml— structured feature request with project dropdownconfig.yml— enables blank issues, adds Security contact linkCopies PR template to
.github/PULL_REQUEST_TEMPLATE.md(same file,inherited path).
Why
Per 2026-04-24 public-repo audit §OSS-readiness-gaps #4
(
~/cog-workspace/.cog/run/trackh/public-repo-audit.md):GitHub surfaces org-default issue templates to member repos only
when they live under
.github/ISSUE_TEMPLATE/inside thecogos-dev/.githubrepo — not at the root-levelISSUE_TEMPLATE/directory this repo currently uses. The existing markdown templates
are a no-op for inheritance; they only apply to this repo itself.
This PR places YAML forms at the correct path so every public repo
(
cogos,mod3,constellation,cog-sandbox-mcp,charts,skills,research) picks them up automatically with no per-repochanges.
Why YAML forms over the old markdown
How
.github/ISSUE_TEMPLATE/with three YAML filesPULL_REQUEST_TEMPLATE.mdto.github/PULL_REQUEST_TEMPLATE.mdISSUE_TEMPLATE/andPULL_REQUEST_TEMPLATE.mdleft inplace (they're a no-op for other repos but still serve this repo)
Verification after merge
cogos-dev/cogos→ should show Bug Reportand Feature Request forms as options, not a blank body.
cogos-dev/mod3→ same.Follow-up (not in this PR)
ISSUE_TEMPLATE/markdown files in afuture cleanup PR once inheritance is verified.