projectdiscovery
diff --git a/‎.github/ISSUE_TEMPLATE/README.md‎
Lines changed: 64 additions & 0 deletions b/‎.github/ISSUE_TEMPLATE/README.md‎
Lines changed: 64 additions & 0 deletions
diff --git a/‎.github/ISSUE_TEMPLATE/config.yml‎
Lines changed: 20 additions & 8 deletions b/‎.github/ISSUE_TEMPLATE/config.yml‎
Lines changed: 20 additions & 8 deletions
diff --git a/‎.github/ISSUE_TEMPLATE/feature_request.md‎ renamed to ‎.github/ISSUE_TEMPLATE/feature_request.md.disabled‎ b/‎.github/ISSUE_TEMPLATE/feature_request.md‎ renamed to ‎.github/ISSUE_TEMPLATE/feature_request.md.disabled‎
diff --git a/‎.github/ISSUE_TEMPLATE/issue-report.md‎ renamed to ‎.github/ISSUE_TEMPLATE/issue-report.md.disabled‎ b/‎.github/ISSUE_TEMPLATE/issue-report.md‎ renamed to ‎.github/ISSUE_TEMPLATE/issue-report.md.disabled‎
diff --git a/‎.github/MAINTAINER_GUIDE.md‎
Lines changed: 164 additions & 0 deletions b/‎.github/MAINTAINER_GUIDE.md‎
Lines changed: 164 additions & 0 deletions
diff --git a/‎.github/workflows/build-test.yml‎
Lines changed: 3 additions & 3 deletions b/‎.github/workflows/build-test.yml‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎.github/workflows/codeql-analysis.yml‎
Lines changed: 1 addition & 1 deletion b/‎.github/workflows/codeql-analysis.yml‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎.github/workflows/compat-checks.yaml‎
Lines changed: 1 addition & 1 deletion b/‎.github/workflows/compat-checks.yaml‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎.github/workflows/dep-auto-merge.yml‎
Lines changed: 1 addition & 1 deletion b/‎.github/workflows/dep-auto-merge.yml‎
Lines changed: 1 addition & 1 deletion
@@ -0,0 +1,64 @@
+# Issue Template Management
+
+## New Issue Workflow (Discussion-First)
+
+To improve issue triage and reduce noise from questions being filed as bugs, all issue creation now goes through GitHub Discussions first.
+
+### For Users:
+
+**❌ Direct issue creation is disabled**
+**✅ All reports must start as discussions**
+
+Users will be redirected to:
+- 🐛 **Bug Reports** → [Q&A Discussions](https://github.com/projectdiscovery/katana/discussions/new?category=q-a)
+- 💡 **Feature Requests** → [Ideas Discussions](https://github.com/projectdiscovery/katana/discussions/new?category=ideas)  
+- ❓ **Questions** → [Q&A Discussions](https://github.com/projectdiscovery/katana/discussions/new?category=q-a)
+
+### For Maintainers:
+
+#### Converting Discussions to Issues:
+
+1. **Review the discussion** thoroughly
+2. **Determine if it's a valid bug/feature** (not just a question)
+3. **Convert to issue** using GitHub's "Convert to Issue" feature:
+   - Go to the discussion
+   - Click "⋯" menu → "Convert to issue"
+   - Add appropriate labels and assignees
+   
+#### Triage Guidelines:
+
+**Convert to Issue:**
+- ✅ Confirmed bugs with reproduction steps
+- ✅ Well-defined feature requests with clear use cases
+- ✅ Security vulnerabilities (after initial assessment)
+
+**Keep as Discussion:**
+- ❌ Usage questions ("How do I...?")
+- ❌ Configuration help
+- ❌ Unclear or incomplete bug reports
+- ❌ Feature ideas that need more discussion/refinement
+
+### Benefits:
+
+- 📊 **Better issue quality** - Only confirmed bugs/features become issues
+- 🎯 **Easier triage** - Questions don't clutter the issue tracker
+- 💬 **Community involvement** - Discussion encourages collaboration before formal issues
+- 🧹 **Cleaner issue tracker** - Focus on actionable items only
+
+## Re-enabling Templates (If Needed)
+
+If you need to temporarily re-enable direct issue creation:
+
+```bash
+# Re-enable templates
+mv issue-report.md.disabled issue-report.md
+mv feature_request.md.disabled feature_request.md
+
+# Update config.yml to add them back
+```
+
+## Template Files:
+
+- `config.yml` - Main configuration (redirects all to discussions)
+- `issue-report.md.disabled` - Bug report template (disabled)
+- `feature_request.md.disabled` - Feature request template (disabled)
@@ -1,14 +1,26 @@
 blank_issues_enabled: false
 
 contact_links:
-  - name: Ask an question / advise on using katana
-    url: https://github.com/projectdiscovery/katana/discussions/categories/q-a
-    about: Ask a question or request support for using katana
+  - name: Report a Bug (Discussion First)
+    url: https://github.com/projectdiscovery/katana/discussions/new?category=q-a
+    about: Report bugs or issues via discussion for proper triage before issue creation
 
-  - name: Share idea / feature to discuss for katana
-    url: https://github.com/projectdiscovery/katana/discussions/categories/ideas
-    about: Share idea / feature to discuss for katana
+  - name: Feature Request (Discussion First)
+    url: https://github.com/projectdiscovery/katana/discussions/new?category=ideas
+    about: Share feature ideas via discussion for evaluation before implementation
 
-  - name: Connect with PD Team (Discord)
+  - name: Ask a Question
+    url: https://github.com/projectdiscovery/katana/discussions/new?category=q-a
+    about: Ask questions about usage, configuration, or troubleshooting
+
+  - name: General Discussion
+    url: https://github.com/projectdiscovery/katana/discussions/new?category=general
+    about: General discussion about the project
+
+  - name: Security Issues
+    url: mailto:security@projectdiscovery.io
+    about: Report security vulnerabilities privately via email
+
+  - name: Discord Community
     url: https://discord.gg/projectdiscovery
-    about: Connect with PD Team for direct communication
+    about: Connect with PD Team and community for real-time discussion
@@ -0,0 +1,164 @@
+# Maintainer Guide: Discussion-First Issue Management
+
+## Overview
+
+Katana now uses a **discussion-first approach** for issue management to improve triage quality and reduce noise from questions being filed as bugs.
+
+## How It Works
+
+### 1. **All Reports Start as Discussions**
+- Users cannot create issues directly
+- All bug reports → **Q&A Discussions**  
+- All feature requests → **Ideas Discussions**
+- All questions → **Q&A Discussions**
+
+### 2. **Automated Triage Helper**
+- Auto-responds to discussions with helpful guidance
+- Auto-flags potential bugs with keywords detection
+- Provides checklists for proper bug reporting
+
+### 3. **Maintainer Conversion Process**
+- Review discussions for completeness
+- Convert valid issues using GitHub's built-in feature
+- Apply appropriate labels during conversion
+
+## Conversion Guidelines
+
+### 🐛 **Bug Reports** → Convert to Issue When:
+
+**Well-Defined Problems:**
+- Clear reproduction steps provided
+- Katana version specified
+- Expected vs actual behavior described  
+- Environment details included
+- Error messages/logs included
+
+**Confirmed Bugs:**
+- Issue reproduced by maintainer or community
+- Not a configuration/usage question
+- Not working as designed
+
+**Keep as Discussion:**
+- Incomplete information
+- Usage questions ("How do I...?")
+- Configuration problems
+- Working as intended
+
+### 💡 **Feature Requests** → Convert to Issue When:
+
+**Solid Proposals:**
+- Clear use case defined
+- Benefits to community explained
+- Implementation approach considered
+- Not easily achievable with existing features
+
+**Community Support:**
+- Multiple users expressing interest
+- Maintainer approval for implementation
+- Fits project roadmap
+
+**Keep as Discussion:**
+- Vague ideas needing refinement
+- Better suited as external tools/plugins
+- Conflicts with project goals
+- Needs more community input
+
+## Conversion Process
+
+### Using GitHub's Convert Feature:
+
+1. **Open the discussion**
+2. **Click the "⋯" menu** (top right)
+3. **Select "Convert to issue"**
+4. **Choose repository** (same repo)
+5. **Review title/body** - edit if needed
+6. **Add labels:**
+   - `Type: Bug` for confirmed bugs
+   - `Type: Enhancement` for approved features  
+   - `Priority: High/Medium/Low` as appropriate
+   - `Component: Engine/Parser/Output` etc.
+
+### Template for Converted Issues:
+
+When converting, consider adding this note:
+
+```markdown
+**Converted from Discussion:** #[discussion_number]
+
+<!-- Original discussion provided community input and initial triage -->
+
+[Original discussion content here]
+
+---
+
+**Maintainer Notes:**
+- [ ] Issue confirmed through discussion
+- [ ] Reproduction steps verified  
+- [ ] Ready for implementation/investigation
+```
+
+## Workflow Benefits
+
+### **For Project Health:**
+- **Cleaner issue tracker** - Only actionable items
+- **Better metrics** - Issues vs discussions clearly separated
+- **Faster resolution** - Less time sorting questions from bugs
+
+### **For Community:**
+- **Inclusive discussions** - Everyone can participate in triage
+- **Better help** - Community can answer questions quickly  
+- **Learning opportunity** - Users see resolution process
+
+### **For Maintainers:**
+- **Pre-filtered issues** - Only valid bugs/features reach issue tracker
+- **Rich context** - Discussion history provides background
+- **Community input** - Others help validate before conversion
+
+## Examples
+
+### **Good Bug Discussion → Issue Conversion**
+
+**Discussion Title:** "Katana crashes when using -hl with custom headers"
+
+**Discussion Body:** 
+- Katana version: v1.2.1
+- Command: `katana -u example.com -hl -H "Custom: value"`
+- Error: panic in hybrid engine
+- Platform: macOS 14.1
+- Reproduction: consistent crash
+
+**→ Convert to Issue:** Clear bug with reproduction steps
+
+### **Question → Keep as Discussion**
+
+**Discussion Title:** "How to crawl only PDF files?"
+
+**Discussion Body:**
+- New user question
+- Asking for usage help
+- Not a bug or feature request
+
+**→ Keep as Discussion:** Usage question, answer in discussion
+
+### **Needs More Info → Keep as Discussion**
+
+**Discussion Title:** "Katana doesn't work"
+
+**Discussion Body:**
+- Vague description
+- No version, command, or error details
+- No reproduction steps
+
+**→ Keep as Discussion:** Request more information first
+
+## Quick Reference
+
+| Type | Action | Labels for Conversion |
+|------|---------|-------------------|
+| **Confirmed Bug** | Convert → Issue | `Type: Bug`, `Priority: [level]` |
+| **Approved Feature** | Convert → Issue | `Type: Enhancement`, `Priority: [level]` |  
+| **Usage Question** | Keep → Discussion | N/A |
+| **Needs Info** | Keep → Discussion | N/A |
+| **Security Issue** | Email → security@projectdiscovery.io | N/A |
+
+This workflow ensures high-quality issues while maintaining an inclusive, helpful community environment!
@@ -14,7 +14,7 @@ jobs:
     if: "${{ !endsWith(github.actor, '[bot]') }}"
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
       - uses: projectdiscovery/actions/setup/go@v1
       - uses: projectdiscovery/actions/golangci-lint@v1
 
@@ -25,15 +25,15 @@ jobs:
     strategy:
       matrix:
         os: [ubuntu-latest, windows-latest, macOS-latest]
-        go-version: [1.21.x]
+        go-version: [1.24.x]
     steps:
       - name: Set up Go
         uses: actions/setup-go@v4
         with:
           go-version: ${{ matrix.go-version }}
 
       - name: Check out code
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Test
         run: go test ./...
 
@@ -26,7 +26,7 @@ jobs:
 
     steps:
     - name: Checkout repository
-      uses: actions/checkout@v4
+      uses: actions/checkout@v5
 
     # Initializes the CodeQL tools for scanning.
     - name: Initialize CodeQL
 
@@ -13,5 +13,5 @@ jobs:
     permissions:
       contents: write
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
       - uses: projectdiscovery/actions/setup/go/compat-checks@v1
@@ -18,7 +18,7 @@ jobs:
     runs-on: ubuntu-latest
     if: github.actor == 'dependabot[bot]'
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
         with:
           token: ${{ secrets.DEPENDABOT_PAT }}