alexleventer/GitHub Issue Due Dates
Label and optionally comment on issues whose YAML frontmatter contains a due date.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| GH_TOKEN | GitHub token used to read issues and manage labels/comments. | yes | — |
| overdue-label | Label applied when an issue is overdue. | no | Overdue |
| upcoming-labels | YAML list of upcoming-due thresholds. Each entry is { days, label }. The smallest-matching threshold wins. Default: a single "Due in 1 week" bucket at 7 days. | no | - days: 7 label: 'Due in 1 week' |
| comment-on-overdue | Optional comment template posted once when an issue becomes overdue. Supports {{daysUntil}}, {{dueDate}}, {{issueNumber}}. Leave empty to disable. | no | "" |
| comment-on-upcoming | Optional comment template posted once when an issue enters an upcoming-due bucket. Same template variables as comment-on-overdue. | no | "" |
| dry-run | If true, log planned changes without calling the GitHub API. | no | false |
Outputs
| name | description |
|---|---|
| issues-processed | Total open issues fetched. |
| issues-changed | Number of issues that had labels or comments updated. |