First pass building an automated workflow for handling wants

[aarongustafson]

Replaces Zapier & manual review

[Copilot]

Pull Request Overview

This PR implements a comprehensive automated workflow for processing want submissions from Netlify forms, replacing the manual Zapier integration. The system automatically receives webhook submissions, creates GitHub issues, and uses GitHub Copilot to intelligently process, categorize, and generate properly formatted want files.

Key changes include:

• Automated webhook processing pipeline from Netlify forms to GitHub issues
• Intelligent want processing using GitHub Copilot with spam detection, relevance checking, and duplicate detection
• Comprehensive documentation for setup, configuration, and maintenance

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
scripts/wantProcessor.js	Core processing utilities for want file generation, duplicate detection, and validation
netlify/functions/package.json	Package configuration for Netlify Functions with modern @netlify/functions dependency
netlify/functions/create-want-issue.mjs	Modern ES module Netlify function to bridge form submissions to GitHub API
docs/NETLIFY_WEBHOOK_SETUP.md	Complete setup guide for webhook configuration and environment variables
docs/MANUAL_PROCESSING.md	Instructions for manually processing existing issues through the automated workflow
docs/AUTOMATED_WORKFLOW_SUMMARY.md	Comprehensive overview of the entire automated system and its benefits
.github/workflows/process-want-submission.yml	GitHub Actions workflow handling webhook events and issue processing
.github/instructions/wants-processing.instructions.md	Detailed processing instructions for GitHub Copilot
.github/ISSUE_TEMPLATE/automated-want-submission.md	Issue template for webhook-generated submissions

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[aarongustafson]

@captainbrosset @ststimac @bkardell @tantek @cwilso @meyerweb In the interest of building a little momentum and allowing us to focus more on high-quality want submissions, I’ve put together a proposed workflow that would allow us to leverage GitHub Copilot to assist with triage and drafting PRs for new wants. I think this will help us with the low availability of time.

Thoughts welcome & appreciated. If there are specific questions or feedback, please include them as part of a review on thie PR.

[tantek]

Added a few things for technologies and IETF as source of references

[tantek]

Curious why "resolved conversation" rather than "committed changes". Otherwise LGTM.

[aarongustafson]

Curious why "resolved conversation" rather than "committed changes". Otherwise LGTM.

I’m not sure what happened either.

[captainbrosset]

Thank you, Aaron. I left a bunch of comments to potentially improve this.
Mostly, I'm interested in seeing it run. I don't have that much technical knowledge of workflows, netlify, or the way github copilot integrates in all this, so I didn't deeply review the code, but I'm curious to see how well this can perform.