You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# GitHub Action for Tracking Issues & Pull Requests
2
2
3
-
## Overview
4
-
A GitHub Action to monitor new issues and pull requests in a specified repository and send notifications to Slack or Discord. This action allows you to track activity in your repositories and get alerted when new issues or PRs are created.
3
+
Managing activity in open-source repositories can be challenging. With a constant influx of **issues** and **pull requests**, it's easy to lose track of what needs attention—especially when working with large teams or active projects. Missed notifications or delayed responses can lead to bottlenecks, reduced contributor satisfaction, and slower project progress.
5
4
6
-
## Features
5
+
## Repo Activity Monitor
7
6
8
-
- Monitor issues and PRs in a GitHub repository.
9
-
- Support for multiple notification methods.
10
-
- Easy integration with GitHub workflows.
7
+
This [GitHub Action](https://github.com/marketplace/actions/repo-monitor) empowers open-source maintainers by:
11
8
12
-
## Inputs
9
+
- Tracking new issues and pull requests in real time.
10
+
- Sending notifications to your preferred communication platforms like **Slack** or **Discord**
13
11
14
-
| Input | Description | Required | Default |
15
-
| ----- | ----------- | -------- | ------- |
16
-
| task | The task to run (monitor-issues or monitor-prs). | Yes | None |
| slack_bot_token | Slack bot token to send notifications (required if notifier=`slack`). | No | None |
23
-
| slack_channel | The Slack channel id to send notifications to (required if notifier=`slack`). | No | None |
24
-
| slack_id_type | Type of Slack ID (user or group, required if notifier=`slack`). This is needed to ping someone directly. | No | None |
25
-
| slack_id | user id or group id as per `slack_id_type` (required if notifier=`slack`). | No | None |
26
-
| discord_webhook_url | Discord webhook URL to send notifications (required if notifier=`discord`). | No | None |
12
+
With **Repo ActivityMonitor**, you can stay on top of your repositories' activities, streamline communication, and ensure no critical issues or pull requests fall through the cracks.
| slack_bot_token | Slack bot token to send notifications (required if notifier=`slack`). | No | None |
92
+
| slack_channel | The Slack channel id to send notifications to (required if notifier=`slack`). | No | None |
93
+
| slack_id_type | Type of Slack ID (user or group, required if notifier=`slack`). This is needed to ping someone directly. | No | None |
94
+
| slack_id | user id or group id as per `slack_id_type` (required if notifier=`slack`). | No | None |
95
+
| discord_webhook_url | Discord webhook URL to send notifications (required if notifier=`discord`). | No | None |
96
+
97
+
## 📖 How It Works
60
98
- The action listens for new issues or PRs in the specified GitHub repository.
61
99
- Depending on the `task` input, it will either monitor new issues (`monitor-issues`) or pull requests (`monitor-prs`).
62
100
- Once a new issue or PR is detected, it sends a notification via Slack or Discord based on the `notifier` input.
63
101
- The action checks for issues or PRs within the time period defined by `fetch_data_interval`, which should align with the cron schedule. For example, if the cron schedule is set to run every hour `(0 * * * *)`, set `fetch_data_interval` to 1 hour.
64
102
65
-
## Setting up Slack
66
-
If you choose Slack as the notification method, you will need to create a Slack app and retrieve the **Slack Bot Token** and **Channel**:
103
+
## 🔧 Setting Up
104
+
105
+
### Slack
106
+
107
+
- Create a Slack App.
108
+
- Generate a Slack Bot Token.
109
+
- Retrieve the Channel ID and User/Group IDs.
110
+
- Add these secrets to your GitHub repository:
111
+
- `SLACK_BOT_TOKEN`
112
+
- `SLACK_CHANNEL`
113
+
- `SLACK_ID_TYPE`
114
+
- `SLACK_ID`
67
115
68
-
- Create a Slack app.
69
-
- Generate a **Slack Bot Token**.
70
-
- Get the **Channel I**D.
71
-
- Get the **Slack User ID** or **Group ID**.
72
-
- Add these tokens/IDs to the GitHub secrets (`SLACK_BOT_TOKEN`, `SLACK_CHANNEL`, `SLACK_ID_TYPE`, and `SLACK_ID`).
116
+
### Discord
73
117
74
-
`slack_id_type`Explanation
75
-
- `user`: Use this if you want to send a notification to an individual user.
76
-
- `group`: Use this if you want to send a notification to a group of users (e.g., a Slack channel or a group).
118
+
- Create a Discord Webhook.
119
+
- Copy the Webhook URL.
120
+
- Add the Webhook URL to your GitHub repository secrets as `DISCORD_WEBHOOK_URL`.
77
121
78
-
## Setting up Discord
79
-
If you choose Discord as the notification method, you will need a Discord Webhook URL:
122
+
## 🔮 Roadmap
80
123
81
-
- Create a **Discord Webhook**.
82
-
- Copy the Webhook URL and add it to the GitHub secrets (`DISCORD_WEBHOOK_URL`).
0 commit comments