Best way to send slack to developers notifications daily about new PRs, new issues or new comments ?

[sagarprateek248]

Select Topic Area

Question

Body

I have thoroughly reviewed the available documentation and community forums, but I was unable to find a satisfactory answer to my query regarding - The Best Possible way to send slack notifications(and email and create jira ticket) daily about new open issues, new open PRs and new comments from external developers(outside organisation). We need to utilise this data daily so that we can be more available to the open source community.

I have tried to find some of the possible ways to achieve the results of the above problem statement. Here are the specific details that I can try to achieve the solution:

Approach 1 -
1.Creation of such service using Github Webhooks
Go to your GitHub repository: Open your repository on GitHub.
Navigate to Settings: Click on the "Settings" tab.
Webhooks: In the left sidebar, click on "Webhooks."
Add a new webhook: Click on the "Add webhook" button.
Payload URL: Create an incoming webhook in your Slack workspace. Go to your Slack channel, click on "Add an app," search for "Incoming WebHooks," and add it to your channel. Copy the Webhook URL provided by Slack.
Paste the URL in GitHub: In the GitHub webhook settings, paste the Slack Webhook URL into the "Payload URL" field.
Content type: Set the content type to application/json.
Select events: Choose the GitHub events that you want to trigger notifications. For pull request-related notifications, select "Let me select individual events" and choose "Pull requests."
Activate the webhook: Click on "Add webhook" to save and activate the webhook.

Approach 2 -
Creation of such service via Github Actions and
Step1: Create a Slack App:Go to Slack API and create a new app for your workspace. Navigate to the "Incoming Webhooks" section and activate it. Add the app to your desired channel to obtain the Webhook URL.
Step 2: Create a GitHub Actions Workflow: Create a Workflow File: In your GitHub repository, create a new file under the .github/workflows/ directory, e.g., .github/workflows/slack-notifications.yml.
Add Workflow Configuration:
Step 3: Create a Node.js Script: Create a Node.js script (e.g., notify-slack.js) in your repository to fetch information about new pull requests and send notifications to Slack.
Step 4: Add Secrets to GitHub Repository: Add Slack Webhook Secret:In your GitHub repository, go to "Settings" -> "Secrets" and add a secret named SLACK_WEBHOOK_URL with the value of your Slack Webhook URL.
Step 5: Customize GitHub API Request: Customize GitHub API Request:Customize the GitHub API request in the Node.js script based on your needs. You may want to filter pull requests based on labels, states, or other criteria.
Step 6: Commit and Push Changes: Commit and Push Changes:Commit the new files (notify-slack.js and the workflow file) and push them to your GitHub repository.
Step 7: Verify Workflow Execution: Verify Workflow Execution:After pushing the changes, the GitHub Actions workflow will be triggered daily at midnight. Check the Actions tab in your GitHub repository to verify that the workflow runs successfully.

My query being - Are there any easy other possible ways or features that Github provides for achieving my usecase?

[pperez]

I believe there's a builtin integration with slack https://slack.github.com/
I'm not sure if it's going to handle every use you want, for instance daily pr reminders, i would say that if it doesn't meet every one of your use cases you can write some simple workflow that uses the github api to grab data from the repo, converts the payload into a slack webhook format and sends it. And you can use reusable workflows to have that in each one of your repos

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[coltenkrauter]

I wanted such a thing, so I wrote the GitHub Notifier https://github.com/marketplace/actions/github-notifier-by-krauters

I'd love feedback (leave an issue – https://github.com/krauters/github-notifier/issues) to expand use cases and support.

[gabriel-pineda]

This is something that me and my team also needed.
This is why we built PullNotifier.

It's been working well for us and our solution seems to also work for a lot of other enterprise orgs as well.