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
* feat: payload change for slack and discord
* feat: added support for discord role and user id
* feat: added preview images
* fix: preview style changed
* feat: preview added
* node updated to 22
* feat: error mechanism added
Copy file name to clipboardExpand all lines: README.md
+50-14Lines changed: 50 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Monitor Issues & PRs with Slack/Discord Notifications
1
+
# Monitor Issues & PRs with Slack+Discord Notifications
2
2
3
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.
4
4
@@ -8,8 +8,9 @@ This [GitHub Action](https://github.com/marketplace/actions/repo-activity-monito
8
8
9
9
- Tracking new issues and pull requests.
10
10
- Sending auto-generated notifications to **Slack** or **Discord**.
11
-
- Customizing Slack notifications with the ability to ping specific users or groups.
12
-
- Allowing Slack notifications to be sent to designated channels.
11
+
- Customizing **Slack** notifications with the ability to ping specific users or groups.
12
+
- Customizing **Discord** notifications with the ability to ping specific users or roles.
13
+
- Allowing **Slack** notifications to be sent to designated channels.
13
14
14
15
With **Repo Activity Monitor**, you can stay on top of your repositories activities, streamline communication, and ensure no critical issues or pull requests fall through the cracks.
15
16
@@ -30,15 +31,15 @@ jobs:
30
31
runs-on: ubuntu-latest
31
32
steps:
32
33
- name: Set up Node.js
33
-
uses: actions/setup-node@v3
34
+
uses: actions/setup-node@v4
34
35
with:
35
-
node-version: '16'
36
+
node-version: '22'
36
37
- name: Monitor New Issues
37
-
uses: shubhaamgupta11/repo-monitor@v0.6.0
38
+
uses: shubhaamgupta11/repo-monitor@v1.0.0
38
39
with:
39
40
# required inputs
40
41
task: "monitor-issues"
41
-
git_secret: "${{ secrets.GITHUB_TOKEN }}"
42
+
git_secret: "${{ secrets.GIT_SECRET }}"
42
43
notifier: "slack"
43
44
fetch_data_interval: 1# Hours (must align with your cron schedule)
44
45
# repo inputs
@@ -68,26 +69,54 @@ jobs:
68
69
runs-on: ubuntu-latest
69
70
steps:
70
71
- name: Set up Node.js
71
-
uses: actions/setup-node@v3
72
+
uses: actions/setup-node@v4
72
73
with:
73
-
node-version: '16'
74
+
node-version: '22'
74
75
- name: Monitor New PRs
75
-
uses: shubhaamgupta11/repo-monitor@v0.6.0
76
+
uses: shubhaamgupta11/repo-monitor@v1.0.0
76
77
with:
77
78
# required inputs
78
79
task: "monitor-prs"
79
-
git_secret: "${{ secrets.GITHUB_TOKEN }}"
80
+
git_secret: "${{ secrets.GIT_SECRET }}"
80
81
notifier: "discord"
81
82
fetch_data_interval: 1# Hours (must align with your cron schedule)
| slack_id_type | Type of Slack ID (user or group, required if notifier=`slack`). This is needed to ping someone directly. | No | None |
104
133
| slack_id | user id or group id as per `slack_id_type` (required if notifier=`slack`). | No | None |
105
134
| discord_webhook_url | Discord webhook URL to send notifications (required if notifier=`discord`). | No | None |
135
+
| discord_id_type | Type of Discord ID (user or role, required if notifier=`discord`). This is needed to ping someone directly. | No | None |
136
+
| discord_id | user id or role id as per `discord_id_type` (required if notifier=`discord`). | No | None |
106
137
107
138
## 📖 How It Works
108
139
- The action listens for new issues or PRs in the specified GitHub repository.
@@ -119,15 +150,17 @@ jobs:
119
150
- Retrieve the Channel ID and User/Group IDs.
120
151
- Add these secrets to your GitHub repository:
121
152
- `SLACK_BOT_TOKEN`
122
-
- `SLACK_CHANNEL`
123
-
- `SLACK_ID_TYPE`
124
-
- `SLACK_ID`
153
+
- Provide the Slack Channel ID, Slack ID Type and Slack ID in the workflow.
125
154
126
155
### Discord
127
156
128
157
- Create a [Discord Webhook](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks).
129
158
- Copy the Webhook URL.
130
159
- Add the Webhook URL to your GitHub repository secrets as `DISCORD_WEBHOOK_URL`.
160
+
- Retrieve the User/Role IDs.
161
+
- Add these secrets to your GitHub repository:
162
+
- `DISCORD_WEBHOOK_URL`
163
+
- Provide the Discord Webhook URL, Discord ID Type and Discord ID in the workflow.
131
164
132
165
## 🔮 Roadmap
133
166
@@ -139,3 +172,6 @@ jobs:
139
172
## 📜 License
140
173
141
174
This project is licensed under the [MIT License](https://github.com/shubhaamgupta11/repo-monitor/blob/main/LICENSE).
175
+
176
+
## Support & Feedback
177
+
If you find this action helpful, please give the repository a ⭐️ on GitHub! Your support helps us grow and continue improving. Feel free to raise issues or suggest enhancements to make this even better.
0 commit comments