-
Notifications
You must be signed in to change notification settings - Fork 21
First pass building an automated workflow for handling wants #769
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…s Zapier & manual review)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
…bWeWant/webwewant.fyi into aarongustafson/want-workflows
@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. |
Replaces Zapier & manual review