netanelcyber / netanelcyber/AdPentestAI-Python
Automate onefile build in CI
Open
Nobody has claimed this yet.
build
ci
- Dominant language
- Python
- Stars
- 5
- Forks
- 2
- Avg merge
- 22h 25m
- Merged PRs (30d)
- 7
Description
Problem
adpentest_onefile.py is currently regenerated by hand via a scratch script. It will drift from the package on any core change.
Proposal
- Move the assembly logic into
scripts/build_onefile.py(checked in) - Add a GitHub Actions job on
pushtomainthat:- Runs the script
- Fails CI if
adpentest_onefile.pydiffers fromHEAD - Runs
python3 -m py_compile adpentest_onefile.pyand a smoke import
Bonus
- Attach the built onefile as a release asset on tag pushes (
v*).
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 scratch script and the current generation path for adpentest_onefile.py, then move that assembly logic into scripts/build_onefile.py. Add a GitHub Actions job for pushes to main that checks the generated file, runs python3 -m py_compile, and performs the smoke import. Done means CI detects drift and validates the generated onefile; the tag-release asset is an optional bonus.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100