enforce VMRay minify script when adding new archives
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
> One downside is that the dynamic VMRay test files tend to be relatively large (a few MB to several dozen MB).
We'd also want to enforce users to leverage our VMRay minify script when adding new VMRay archives.
_Originally posted by @mike-hunhoff in https://github.com/mandiant/capa/issues/2410#issuecomment-2386407267_
via script / GitHub Action
Contributor guide
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 locating the existing VMRay minify script and the workflow used when archives are added. Define how a GitHub Action or script should enforce minification for new VMRay archives, then verify that an unminified archive is rejected and a minified archive passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100