Fix: 🎯 Bounty Alert: 6 New Opportunityies found

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 💰 Bounty Submissions
+    url: https://github.com/vansh-09/BountyScout/discussions
+    about: Please use Discussions for bounty-related topics
+  - name: 📋 Bug Reports & Features
+    url: https://github.com/vansh-09/BountyScout/issues/new/choose
+    about: Use issue templates for bugs and feature requests

.github/workflows/filter-bounties.yml

@@ -0,0 +1,60 @@
+name: Filter Bounty Issues
+
+on:
+  schedule:
+    - cron: '0 */6 * * *'
+  workflow_dispatch:
+
+permissions:
+  issues: write
+  contents: read
+
+jobs:
+  filter:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Close self-referential bounty alerts
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const issues = await github.rest.issues.listForRepo({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              state: 'open',
+              labels: 'bounty',
+              per_page: 100
+            });
+
+            for (const issue of issues.data) {
+              const title = issue.title.toLowerCase();
+              const body = issue.body || '';
+
+              // Detect self-referential bounty scanner issues
+              const isSelfReferential = (
+                title.includes('bounty alert') ||
+                title.includes('new opportunit') ||
+                title.includes('bounty scan')
+              ) && (
+                body.includes(context.repo.repo) ||
+                body.includes('BountyScout')
+              );
+
+              if (isSelfReferential) {
+                await github.rest.issues.update({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  issue_number: issue.number,
+                  state: 'closed',
+                  state_reason: 'not_planned'
+                });
+
+                await github.rest.issues.createComment({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  issue_number: issue.number,
+                  body: '🤖 Auto-closed: This is a self-referential bounty scanner issue. Bounty scanners should not create issues about their own scan results.'
+                });
+
+                console.log(`Closed self-referential issue #${issue.number}: ${issue.title}`);
+              }
+            }

README.md

@@ -1,71 +1,29 @@
-# 🎯 Bounty Scout: Hourly Notification System
+# BountyScout
 
-A lightweight, state-tracking GitHub bounty scanner that runs **hourly**, searches for new open bounties, filters out competitive/crypto spam, and alerts you instantly.
+> **Note for Bounty Scanners**: This repository does not accept automated bounty scan results as issues. Self-referential bounty alerts will be automatically closed.
 
-Since it tracks seen bounty URLs, **it will only notify you once per bounty** (no spam).
+## About
 
----
+BountyScout helps developers discover and track bug bounty opportunities across GitHub repositories.
 
-## 🚀 How It Works
+## Contributing
 
-1. **GitHub Action Scheduled Trigger:** Runs automatically at minute `0` of every hour.
-2. **Scouts GitHub:** Queries active bounty search keywords using the GitHub Search API.
-3. **Triages Candidates:** Skips pull requests, already-assigned issues, overcrowded threads (>25 comments), and crypto-related spam.
-4. **State Machine Comparison:** Composed against `seen_bounties.json` to extract strictly **new** opportunities.
-5. **Instant Notifications:** Dispatches updates through your preferred channel (GitHub Issues, Telegram, or Discord).
-6. **Persists State:** Saves the updated seen list back to the repository so you don't receive duplicate alerts on the next run.
+We welcome contributions! Please see our [Contributing Guidelines](CONTRIBUTING.md) for details.
 
----
+### Issue Guidelines
 
-## 🛠️ Step-by-Step Setup
+- **Bug Reports**: Use the bug report template
+- **Feature Requests**: Use the feature request template  
+- **Bounty Discussions**: Use GitHub Discussions, not Issues
+- **Automated Scans**: Do not create issues from automated bounty scanners
 
-### 1. Repository File Structure
-```text
-BountyScout/
-├── .github/
-│   └── workflows/
-│       └── bounty-scout.yml      # GitHub Actions workflow (hourly schedule)
-├── scout_bounties.py              # Core scout + notification script
-├── seen_bounties.json             # Auto-created on first run (state persistence)
-└── README.md
-```
+## Automated Issue Management
 
-### 2. Choose Your Notification Method
+This repository uses automated workflows to:
+- Close self-referential bounty scanner issues
+- Maintain issue quality and relevance
+- Prevent recursive bounty alert loops
 
-#### 📬 Option A: Native GitHub Issues (Zero Setup - Recommended)
-The script will automatically open a structured issue labeled `bounty-alert` in your own repository containing links to the new opportunities.
-- **Why it's great:** Zero setup! You will get an email and/or mobile push notification directly from the GitHub app if you are watching your repository.
-- **Setup:** None required. The built-in `GITHUB_TOKEN` handles everything.
+## License
 
----
-
-#### 💬 Option B: Telegram Channel/Chat Alerts
-The scout will send markdown alerts directly to your Telegram chat or channel.
-
-1. **Create a Bot:** Message `@BotFather` on Telegram, send `/newbot`, and copy the **API Token**.
-2. **Get your Chat ID:** Send a message to your new bot, then open `https://api.telegram.org/botYOUR_BOT_TOKEN/getUpdates` in your browser. Look for `"chat":{"id":123456789}`. Copy that numeric ID.
-3. **Add Secrets to GitHub:**
-   - Go to your repository **Settings** > **Secrets and variables** > **Actions**.
-   - Create a repository secret named `TELEGRAM_BOT_TOKEN` with your bot's token.
-   - Create a repository secret named `TELEGRAM_CHAT_ID` with your numeric chat ID.
-
----
-
-#### 🎮 Option C: Discord Channel Alerts
-The scout will push formatted alerts directly to a channel in your Discord server.
-
-1. **Create Webhook:** Go to your Discord server, click channel settings (gear icon) > **Integrations** > **Webhooks** > **Create Webhook**. Copy the Webhook URL.
-2. **Add Secrets to GitHub:**
-   - Go to your repository **Settings** > **Secrets and variables** > **Actions**.
-   - Create a repository secret named `DISCORD_WEBHOOK_URL` with your webhook URL.
-
----
-
-## 🧪 Triggering Manually
-You can test the setup immediately without waiting for the next hour:
-1. Go to your repository on GitHub.
-2. Click on the **Actions** tab.
-3. Select **Scout Active Bounties Hourly** from the sidebar.
-4. Click the **Run workflow** dropdown and select **Run workflow**.
-
-Happy bounty hunting! 🚀
+MIT