mandiant / mandiant/VM-Packages
Automate dependencies in package creation
Open
Nobody has claimed this yet.
:gem: enhancement
:runner: CI
- Dominant language
- PowerShell
- Stars
- 246
- Forks
- 98
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 7
Description
Details
At the moment we have a dependencies field in the ISSUES TEMPLATES but we are not using it in the automation. To automate it we need to:
- Modify the code in
create_package_template.pyto add the dependencies received as optional argument to the nuspec - Modify all the ISSUE TEMPLATES to improve the description of the
dependenciesfield to ensure the format the user needs to use is clear
Related issues: https://github.com/mandiant/VM-Packages/issues/1082
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 with create_package_template.py and inspect how package arguments are passed into the nuspec. Then review all ISSUE TEMPLATES to identify the dependencies field descriptions. Done means the optional dependencies argument is included in the nuspec and each template clearly documents the required format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100