Skip to content

docs: governance - Document no-auto-closure policy #1164

Description

@ashleyshaw

file_type: "issue-template"
name: "🏠 Chore"
about: "Small housekeeping tasks: label hygiene, repo/settings tweaks, file moves, or minor non-functional clean-ups."
version: "1.0.3"
last_updated: "2026-06-19"
category: "github-templates"

Chore Summary

Scope / Affected Areas

Steps / Checklist

  • Task is clearly defined and actionable
  • Does not fit the Code Refactor or Maintenance templates
  • Documentation updated if affected
  • PR uses correct branch prefix (chore/)
  • Approved by at least one maintainer

Acceptance Criteria

  • Task completed and verified in the affected areas
  • No regressions introduced

Additional Context


Definition of Ready (DoR)

  • Task/goal described and scoped
  • Confirms it does not fit the Code Refactor or Maintenance templates
  • Acceptance criteria listed
  • Estimate added (if applicable)

Definition of Done (DoD)

  • Affected files, labels, or settings updated and documented
  • PR uses correct branch prefix (chore/)
  • Approved by at least one maintainer


Related issues: {related_issues}

Activity

  1. linear-code commented on Jul 23, 2026

    @linear-code
  2. github-actions commented on Jul 23, 2026

    @github-actions
    Contributor

    ✅ Template check passed after update. Thanks for fixing the issue body.

  3. added this to the v1.0 milestone on Jul 23, 2026
  4. github-actions commented on Jul 23, 2026

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 0 day(s)
    • SLA state: Within SLA
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-07-23T16:18:00.330Z

    Maintained by project-meta-sync workflow.

  5. modified the milestones: v1.0, v1.6 on Jul 23, 2026
  6. changed the title [-]docs: document explicit no-auto-closure policy in CLAUDE.md[/-] [+]docs: governance - Document no-auto-closure policy[/+] on Sep 8, 2026
  7. github-actions commented on Sep 8, 2026

    @github-actions
    Contributor

    ⚠️ Bare Labels Detected

    This issue has labels that are not in the canonical taxonomy:

    • priority:high
    • area:governance

    Valid Canonical Labels

    Please use labels with a prefix from the canonical taxonomy:

    • Type: type:bug, type:feature, type:task, type:documentation, etc.
    • Status: status:needs-triage, status:in-progress, status:done, etc.
    • Priority: priority:critical, priority:high, priority:normal, priority:low
    • Area: area:ci, area:docs, area:labels, area:security, etc.
    • Meta: meta:needs-changelog, meta:duplicate, meta:blocked, etc.

    For the complete list, see .github/labels.yml.

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

Metadata

Metadata

Assignees

Fields

Priority

None yet

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions