ConduitIO / ConduitIO/automation
Re-triage issues that we deem not to fix now or next.
Open
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
When triaging issues, we may deem it necessary to do it later. Have a github action that reviews old issues and if they're 2 months old, they will show up in the triage column again for us to reprioritize.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the repository's existing GitHub Actions and the current issue-triage process. The work is done when issues that have remained deferred for two months are automatically surfaced in the triage column for reprioritization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100