- Added document start markers (---) to all YAML files
- Fixed line length issues by breaking long lines appropriately
- Removed trailing whitespace throughout all files
- Added proper newlines at end of files
- Fixed truthy value format ('on' -> 'on')
- Standardized YAML formatting across workflows and issue templates
- Used multi-line strings (>) for long descriptions
- Maintained readability while adhering to 80-character line limit
All YAML files now pass yamllint validation with only minor warnings remaining.
Problem Analysis:
- Original workflow used complex GitHub search API causing rate limiting issues
- Custom first-time contributor detection was unreliable and fragile
- Used pull_request instead of pull_request_target for PRs (security issue)
- Complex github-script logic prone to failures
Solution Implemented:
- Replaced custom logic with GitHub's official actions/first-interaction@v1
- Changed to pull_request_target for PR security and reliability
- Eliminated API rate limiting issues by removing search calls
- Simplified permissions and workflow structure
- Added comprehensive welcome messages with community guidelines
Benefits:
- More reliable first-time contributor detection
- No rate limiting issues
- Better security with pull_request_target
- Easier to maintain using official GitHub action
- Consistent messaging across issues and PRs
Also included alternative implementation example using garg3133/welcome-new-contributors@v1.2
- Added Code of Conduct with clear behavioral standards
- Created Contributing guidelines with submission requirements
- Implemented structured issue templates (bug reports, features, new agents, moderation)
- Disabled blank issues to enforce template usage
- Added automated content moderation via GitHub Actions:
* Real-time scanning for hate speech, threats, and profanity
* Automatic closure/locking of critical violations
* Moderation alerts for maintainer review
- Set up welcome system for new contributors with community guidelines
- Enabled GitHub Discussions as alternative to issues for general questions
- Closed and locked existing hate speech issue #30
- Blocked offending user account
This creates a multi-layered defense against inappropriate content while
maintaining an open, welcoming environment for legitimate contributors.
