timb-machine / timb-machine/linux-malware
Update new_issue.yml to process just the issue that has changed
Open
Nobody has claimed this yet.
bug
enhancement
good first issue
help wanted
- Dominant language
- HTML
- Stars
- 1.2k
- Forks
- 95
- 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
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the new_issue.yml workflow and identify how it currently selects issues to process. Update the workflow so a change processes only the issue that triggered it, then verify that unrelated issues are no longer fetched or reprocessed and API usage is reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100