GitHub Release Monitor and Slack Notifier

This workflow is ideal for:

• Developers: Who want to automate the tracking of GitHub releases for multiple repositories.
• Project Managers: Looking to stay updated on the latest features and fixes from repositories they manage.
• DevOps Teams: Needing to streamline communication about software updates within their organization.
• Tech Enthusiasts: Interested in following the latest developments in open-source projects.

This workflow addresses the challenge of manually monitoring GitHub releases across multiple repositories. It automates the process of checking for new releases, extracting relevant information, and notifying team members via Slack, thereby saving time and ensuring that no important updates are missed.

1. Trigger: The workflow is triggered every 10 minutes between 9 AM and 11 PM daily using a Cron Trigger.
2. Fetch GitHub Config: It retrieves a list of repositories to monitor from the GitHub Config node.
3. Loop Through Repositories: For each repository, it uses the Split In Batches node to process them one by one.
4. Read RSS Feed: The workflow reads the RSS feed for releases from the GitHub repository using the RSS for Release node.
5. Check for Errors: It checks if there were any errors in fetching the data, using the If No Error node.
6. Redis Cache: It retrieves the last known release ID from Redis to compare against the current release.
7. Determine New Releases: If a new release is detected (i.e., the ID is different), it processes the release information.
8. Information Extraction: The Information Extractor node analyzes the release notes, filtering and categorizing the changes into features, fixes, and other relevant notes.
9. Format Date: The release publication date is formatted for better readability.
10. Send Notifications: Finally, the workflow sends a formatted message to a designated Slack channel using the Send Message node, notifying the team of the new release.