Initial release: Top-tier GitHub issue management bot

Author: bijanmurmu

.github/workflows/anti-hoarder.yml

@@ -0,0 +1,67 @@
+name: "Anti-Hoarder Stale Check"
+on:
+  schedule:
+    - cron: '0 0 * * *' # Runs every day at midnight UTC
+  workflow_dispatch: # Allows manual trigger from the Actions tab
+
+jobs:
+  stale-check:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+      - name: Unassign stale issues
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const daysToStale = 14; // Number of days before unassigning
+            const msInDay = 24 * 60 * 60 * 1000;
+            const thresholdDate = new Date(Date.now() - (daysToStale * msInDay));
+
+            // Find open issues with the 'in-progress' label
+            const { data: issues } = await github.rest.issues.listForRepo({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              state: 'open',
+              labels: 'in-progress'
+            });
+
+            for (const issue of issues) {
+              const updatedAt = new Date(issue.updated_at);
+              if (updatedAt < thresholdDate && issue.assignees.length > 0) {
+                // Issue is stale! Unassign everyone
+                const assignees = issue.assignees.map(a => a.login);
+                
+                await github.rest.issues.removeAssignees({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  issue_number: issue.number,
+                  assignees: assignees
+                });
+
+                try {
+                  await github.rest.issues.removeLabel({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    issue_number: issue.number,
+                    name: 'in-progress'
+                  });
+                } catch (e) {
+                  // Ignore if label doesn't exist
+                }
+
+                await github.rest.issues.addLabels({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  issue_number: issue.number,
+                  labels: ['help wanted']
+                });
+
+                await github.rest.issues.createComment({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  issue_number: issue.number,
+                  body: `🚨 This issue has been inactive for over ${daysToStale} days. I am automatically unassigning the current assignees so someone else can pick this up. If you are still working on this, feel free to \`/claim\` it again!`
+                });
+              }
+            }

.gitignore

@@ -0,0 +1,3 @@
+node_modules/
+.env
+*.log

README.md

@@ -0,0 +1,22 @@
+# Orbit-btw-bot
+
+A top-tier GitHub App built with [Probot](https://github.com/probot/probot) that beautifully automates and manages issues for the `Orbit-btw` organization.
+
+## Features & Automation
+- **Single Issue Limit:** Prevents contributors from hoarding tasks. A user can only claim 1 open issue at a time per repository.
+- **Auto-Labeling:** Automatically adds `in-progress` and removes `help wanted` labels when an issue is claimed. 
+- **Smart Reactions:** Reduces comment spam by reacting to commands with emojis (🚀, 👀, ❤️) instead of posting new comments.
+- **Welcome Wagon:** Greets first-time issue creators and commenters to the organization.
+
+## Available Commands
+
+| Command | Description | Access Level |
+|---------|-------------|--------------|
+| `/claim` or `/assign` | Claims the issue. Fails if you already have an active issue. Adds labels and reacts with 🚀 | Anyone |
+| `/unclaim` or `/unassign` | Drops your claim on the issue. Reverts labels to `help wanted`. | Assignees |
+| `/close` | Instantly closes the issue. | Org Members |
+| `/label <name>` | Quickly adds a specific label to the issue (e.g. `/label bug`). | Org Members |
+| `/unlabel <name>`| Quickly removes a specific label from the issue. | Org Members |
+
+## Setup & Deployment
+See [SETUP.md](./SETUP.md) for instructions on how to configure, run, and host this bot 24/7.

SETUP.md

@@ -0,0 +1,65 @@
+# Orbit-btw-bot Setup Guide
+
+Follow these concise steps to set up, register, and run your GitHub App.
+
+## 1. Setup Local Webhook Proxy (Smee)
+GitHub needs a public URL to send events to your local machine.
+1. Go to [https://smee.io/](https://smee.io/) and click **"Start a new channel"**.
+2. Copy the **Webhook Proxy URL** (e.g., `https://smee.io/AbCdEfG...`).
+3. In your `orbit-bot` folder, ensure your `.env` file contains:
+   ```env
+   WEBHOOK_PROXY_URL=https://smee.io/your_channel_id
+   ```
+
+## 2. Auto-Register the App (Recommended)
+Probot can automatically create the App in GitHub and download its keys.
+1. Open your terminal in the `orbit-bot` folder and run `npm run dev`.
+2. Open [http://localhost:3000](http://localhost:3000) in your web browser.
+3. Click **"Register GitHub App"**.
+4. Select the **Orbit-btw** organization.
+5. GitHub will redirect you back, and automatically populate your `.env` file with your `APP_ID`, `PRIVATE_KEY`, and `WEBHOOK_SECRET`.
+
+*(If this works, skip to Step 4!)*
+
+---
+
+## 3. Manual Registration (Only if Auto-Register Fails)
+If the button fails, you must create the App on GitHub manually.
+1. Go to **GitHub -> Orbit-btw (Org) -> Settings -> Developer Settings -> GitHub Apps -> New GitHub App**.
+2. **App Name**: `orbit-btw-bot` (must be unique).
+3. **Homepage URL**: `https://github.com/Orbit-btw`
+4. **Webhook URL**: Paste your Smee proxy URL here.
+5. **Webhook Secret**: Create a random password (e.g., `my_secret_123`).
+6. **Permissions**: 
+   - Set **Issues** to `Read & write`.
+   - Set **Pull requests** to `Read & write`.
+7. **Subscribe to events**: 
+   - Check the boxes for `Issues`, `Issue comment`, and `Pull request`.
+8. Click **Create GitHub App**.
+9. On the next page, click **Generate a private key**. A `.pem` file will download to your computer.
+10. Update your `.env` file manually:
+    ```env
+    WEBHOOK_PROXY_URL=https://smee.io/your_channel_id
+    APP_ID=123456 (Find this on the GitHub App page)
+    WEBHOOK_SECRET=my_secret_123
+    PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----\nYourKeyHere\n-----END RSA PRIVATE KEY-----"
+    ```
+
+## 4. Run and Test Locally
+1. Restart your server: Press `Ctrl + C` in the terminal, then run `npm run dev` again.
+2. Go to any issue in your GitHub repositories.
+3. Comment `/claim` or `/assign` on the issue.
+4. Your bot will automatically assign the issue to you!
+
+## 5. Deployment (Production)
+Once you are ready to run the bot 24/7 without keeping your computer on:
+1. Push this repository to GitHub.
+2. Connect the repository to a hosting provider like [Render](https://render.com/).
+3. Set the start command to `npm start`.
+4. Add the following **Environment Variables** to your hosting provider (copy values from your local `.env` file):
+   - `APP_ID`
+   - `WEBHOOK_SECRET`
+   - `PRIVATE_KEY` (Include the entire `-----BEGIN...` block)
+   *(Note: You do NOT need the `WEBHOOK_PROXY_URL` variable in production)*
+5. **Crucial Final Step:** Once deployed, go back to your **GitHub App Settings**. Change the **Webhook URL** from your `smee.io` link to your new live URL appended with `/api/github/webhooks`. 
+   - Example: `https://your-app-name.onrender.com/api/github/webhooks`

app.yml

@@ -0,0 +1,11 @@
+name: orbit-btw-bot
+description: "A GitHub App to manage issues via comments"
+url: "https://github.com/Orbit-btw"
+public: false
+default_permissions:
+  issues: write
+  pull_requests: write
+default_events:
+  - issue_comment
+  - issues
+  - pull_request

index.js

@@ -0,0 +1,10 @@
+/**
+ * @param {import('probot').Probot} app
+ */
+module.exports = (app) => {
+  app.log.info("Orbit-btw-bot was loaded!");
+
+  // Load modules
+  require('./src/welcome')(app);
+  require('./src/commands')(app);
+};