GitHub is a popular platform used by developers to collaborate on software projects. However, it can be challenging to keep track of all the activities and events across multiple repositories. GitHub's built-in notification system may not always meet everyone's specific needs.
The purpose of this project is to simplify the process of receiving GitHub notifications. With GitHub Event Notifications, you will automatically receive notifications for events like new issues, pull requests, comments, and releases in your Telegram messenger. This way, you can stay up to date with the latest developments and never miss important updates.
Whether you're a developer working on multiple repositories, a team member interested in specific issues, or a project maintainer keeping an eye on pull requests, GitHub Event Notifications makes it easy to enhance your GitHub experience and improve your workflow efficiency.
In this repository, you'll find all the information and resources you need to set up and use the GitHub Event Notifications tool. Get started and ensure that you're always in the loop with GitHub events.
For more API usages: https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads
- Fork this project
- Sign up/in into Deno Deploy
- Create a new project
- Select the forked project
- Select the main branch (or your custom one)
- Name your project
- Add 2 environment variables:
- Go to dashboard and select a newly created project
- Copy deploy domain which does not contain random id
- ✅ your-project-name.deno.dev
- ❌ your-project-name-1234567890ab.deno.dev
- Go to your organization page -> settings -> webhooks (https://github.com/organizations//settings/hooks)
- Add new webhook
- Click on "Add webhook" button
- Payload URL: insert deploy domain from step 5
- Secret: insert WEBHOOK_SECRET from step 3
- Content type: application/json
- SSL verification: enable
- Which events would you like to trigger this webhook: choose your preferred
- Check Active checkbox
- PROFIT!
Reminder! If you forget WEBHOOK_SECRET token, feel free to regenerate and change tokens as this service won't work without it.