GitHub Issue Comment-Limit Headroom and Lockout Forecast
Pricing
$10.00 / 1,000 issue checkeds
GitHub Issue Comment-Limit Headroom and Lockout Forecast
Forecast the date when a GitHub issue reaches the 2,500 comment limit.
Pricing
$10.00 / 1,000 issue checkeds
Rating
0.0
(0)
Developer
kingii98
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
8 days ago
Last modified
Categories
Security
Limited permissionsShare
GitHub rejects new comments on an issue after 2,500 comments. This Actor shows how many comments remain. It forecasts the date when the issue reaches the limit. Use it to move a long thread before comments fail.
Input
| Field | Description | Default |
|---|---|---|
issueUrls | Up to 100 public issue URLs. | One example issue |
repositoryUrl | Optional. One public repository. The Actor checks its issues with the most comments. It replaces issueUrls. | none |
minComments | Repository mode only. Skip issues with fewer comments. | 1 |
maxIssues | Maximum issues for one run (1 to 100). | 100 |
warningThreshold | Comment count that sets the status warning. | 2000 |
githubToken | Optional. Your own token for a higher GitHub API rate limit. The Actor sends it only to api.github.com. | none |
An empty input {} runs the default example and succeeds.
Output
The Actor writes one dataset row for each issue.
| Field | Meaning |
|---|---|
issueUrl, number, title, state | The issue. |
commentCount | Comments now. |
remainingComments | 2,500 minus commentCount. Minimum 0. |
commentsPerDay | Comment count for each of the last 7 UTC days. |
commentsLast7Days, averagePerDay | Total and mean rate. Both use the window that starts at 00:00 UTC, 6 days before today, and ends now. commentsLast7Days equals the sum of commentsPerDay. |
rateIsEstimate | true when the Actor did not fetch all comments of the window. The Actor fetches the newest comments, at most 2 pages of 100 comments. The oldest fetched comment is then newer than the window start, and the rate uses the time span of the fetched comments. |
forecastLockoutDate | Date (UTC) when the issue reaches 2,500 comments at the current rate. null when there is no rate, or when the date is more than 10 years away. |
daysToLockout | Days to that date. |
status | ok, warning, locked, or unavailable. |
message | Reason, for an unavailable row. |
Status rules:
locked: 2,500 comments or more.warning: comment count is at or abovewarningThreshold.ok: all other issues.unavailable: the Actor could not check the issue. Reasons: bad URL, issue not public, redirect, or GitHub API rate limit.
A bad target or an unavailable issue is a dataset row and a status message. The run still succeeds.
Pricing event
The Actor uses pay-per-event pricing with one event.
| Event | Charged when | Count |
|---|---|---|
issue-checked | The Actor writes a headroom row (ok, warning, or locked). | 1 for each issue |
The Actor does not charge for unavailable rows. The Actor stops when the maximum charge limit is reached. Each issue costs one issue request and at most two comment-page requests.
This README does not set a price. Pricing is set outside this repository.
Limits
- Input limit: 100 issues for each run.
- Only
https://github.com/OWNER/REPO/issues/NUMBERURLs are accepted. All requests go toapi.github.com. - The Actor does not follow redirects. Response size limit: 2 MB. Request timeout: 20 seconds. Concurrency: 5.
- The 2,500 comment limit comes from public issue reports. GitHub can change it. Check the constant
COMMENT_LIMITinsrc/logic.py. - The Actor keeps no state. It calculates the rate from comment timestamps. Use an Apify schedule to run it each day.
- Without a token, the GitHub API rate limit is low (60 requests each hour). One issue uses up to 3 requests.
Development
