Skip to content

FTUE: issue template(s) — security reports → SECURITY.md #31

Description

@CodeSolutionsLLC

Parent: #29

Why

No issue templates; community health gap (review L4). Security reports should be steered to SECURITY.md / private vulnerability reporting.

Suggested work

  • Add .github/ISSUE_TEMPLATE/ (bug / docs / other)
  • Security path: link SECURITY.md and private vulnerability reporting; do not ask for secrets in issues

Refs

  • local security review artifact (L4)

Activity

  1. CodeSolutionsLLC commented on Sep 27, 2026

    @CodeSolutionsLLC
    OwnerAuthor

    ASSIGNED — Sam (coding seat)

    Acceptance

    • Add .github/ISSUE_TEMPLATE/ (bug / docs / other as appropriate)
    • Security path steers to SECURITY.md / private vulnerability reporting; do not ask for secrets in issues
    • Public-safe language (#36): no roster names, private tracker links, or internal jargon
    • Poteto draft PR; CI green; no merge; READY → Computer Human VERIFY + Code merge
    • Out of scope: Soft pull KEEP OUT / private CI tooling into cs-stack

    Parent: #29

  2. CodeSolutionsLLC commented on Sep 27, 2026

    @CodeSolutionsLLC
    OwnerAuthor

    Human VERIFY PASS on leaf #31 → PR #40. Awaiting Code merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions