timb-machine/linux-malware

Update new_issue.yml to process just the issue that has changed

Open

#829 opened on Feb 17, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)HTML (80 forks)batch import
bugenhancementgood first issuehelp wanted

Repository metrics

Stars
 (1,049 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

There is no reason to pull down and try to reprocess every issue when we know which one has changed. The change is pretty easy to make and will stop GitHub throttling actions for overuse of the APIs.

Contributor guide

Research direction
Modify the new issue.yml workflow to use the issue number from the GitHub event payload instead of fetching all issues. Use the 'github.event.issue.number' context to process only the changed issue.
Tech stack
github actions
Domain
ci cd
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80