This repository contains organization-level GitHub configurations that are automatically applied to all repositories in the neeve-ai organization.

We provide 5 comprehensive issue templates to ensure consistent and high-quality issue reporting across all our projects:

• File: .github/ISSUE_TEMPLATE/bug-report.yml
• Purpose: Report bugs and unexpected behavior
• Auto-labels: type: bug, status: triage
• Features:
  • Severity classification (Critical/High/Medium/Low)
  • Environment details collection
  • Step-by-step reproduction guides
  • Pre-submission validation checklist

• File: .github/ISSUE_TEMPLATE/feature-request.yml
• Purpose: Suggest new features and enhancements
• Auto-labels: type: feature, status: triage
• Features:
  • User story format
  • Priority and complexity assessment
  • Acceptance criteria definition
  • Mockup/example attachments

• File: .github/ISSUE_TEMPLATE/security-issue.yml
• Purpose: Report security vulnerabilities
• Auto-labels: type: security, status: triage, priority: high
• Features:
  • Security severity classification
  • Vulnerability categorization
  • Impact assessment
  • Responsible disclosure guidelines

• File: .github/ISSUE_TEMPLATE/documentation.yml
• Purpose: Report documentation issues or improvements
• Auto-labels: type: documentation, status: triage
• Features:
  • Documentation type classification
  • Target audience identification
  • Current vs. suggested content comparison
  • Priority assessment

• File: .github/ISSUE_TEMPLATE/general-issue.yml
• Purpose: Catch-all for issues that don't fit other categories
• Auto-labels: type: general, status: triage
• Features:
  • Flexible categorization
  • Context and background collection
  • Priority assessment
  • Related resources tracking

• File: .github/ISSUE_TEMPLATE/config.yml
• Disables blank issues to ensure all issues use templates
• Provides helpful contact links for:
  • Community discussions
  • Feature discussions
  • Private security reporting

• File: .github/stale.yml
• Stale marking: After 75 days of inactivity
• Auto-close: After 90 days total (75 + 15)
• Exemptions: Critical issues, in-progress work, security issues
• Rate limiting: 30 actions per hour

• status: triage - New issues requiring initial review
• status: confirmed - Validated issues ready for work
• status: in-progress - Currently being worked on
• status: blocked - Waiting for dependencies
• status: review - Under review/testing
• status: stale - Marked by stale bot
• status: completed - Work finished

• type: bug - Bug reports
• type: feature - Feature requests
• type: security - Security issues
• type: documentation - Documentation issues
• type: general - General issues

• priority: critical - Urgent issues
• priority: high - Important issues
• priority: medium - Standard priority
• priority: low - Nice-to-have items

• component: ui - User interface related
• component: api - API related
• component: core - Core functionality
• component: docs - Documentation related

New Issue Created
      ↓
[status: triage] ← Auto-applied by template
      ↓
   Team Review
      ↓
┌─────────────────┐
│ Valid Issue?    │
└─────────────────┘
    Yes ↙    ↘ No
         ↙      ↘
[status: confirmed] [closed: invalid]
      ↓
  Prioritized & Assigned
      ↓
[status: in-progress]
      ↓
┌─────────────────┐
│ Blocked?        │
└─────────────────┘
    Yes ↙    ↘ No
         ↙      ↘
[status: blocked] Continue Development
      ↓           ↓
  Dependencies   Work Completed
  Resolved       ↓
      ↓          [status: review]
[status: in-progress] ↓
                Testing & Approval
                     ↓
                [status: completed]
                     ↓
                   Closed

• Issues become stale after 75 days of inactivity
• Stale issues are closed after 15 additional days (90 days total)
• Exemptions for active work, critical issues, and security matters
• Helpful comments guide users on how to keep issues open

• All templates automatically apply appropriate type and status labels
• Security issues get high priority by default
• Consistent labeling across all repositories

1. These templates are automatically available in all neeve-ai repositories
2. No additional setup required
3. Customize labels in individual repositories if needed
4. Monitor and triage issues using the status labels

1. Visit any neeve-ai repository's Issues tab
2. Click "New Issue"
3. Select the appropriate template
4. Fill out all required fields
5. Submit your issue

For critical security vulnerabilities:

1. Email: security@neeve-ai.com (private reporting)
2. Use GitHub's private vulnerability reporting (if available)
3. Only use public Security Issue template for minor/known issues

• Discussions: Use repository discussions for questions
• Feature Ideas: Discuss in feature discussion categories
• General Help: Create a General Issue

• Security Issues: security@neeve-ai.com
• Organization Issues: Create an issue in this repository

1. Edit files in .github/ISSUE_TEMPLATE/
2. Test changes in a repository
3. Document changes in this README
4. Templates automatically propagate to all repositories

• Modify .github/stale.yml
• Adjust timing, exemptions, or messages as needed
• Changes take effect on next bot run

Note: This configuration applies to all repositories in the neeve-ai organization. Individual repositories can override these templates by creating their own .github/ISSUE_TEMPLATE/ directory.

For questions about this configuration, please create an issue in this repository.