vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-21 08:15:23 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[PR #275] [MERGED] docs: add OpenVAS custom image guide #288

New Issue
Closed
opened 2026-06-06 22:10:04 -04:00 by yindo · 0 comments
yindo commented 2026-06-06 22:10:04 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/vxcontrol/pentagi/pull/275
Author: @mason5052
Created: 4/22/2026
Status: ✅ Merged
Merged: 4/28/2026
Merged by: @asdek

Base: feature/next-release ← Head: codex/issue-69-openvas-custom-image-guide

📝 Commits (2)

  • 3e4e800 docs: add OpenVAS custom image guide
  • fb607a8 Merge branch 'feature/next-release' into codex/issue-69-openvas-custom-image-guide

📊 Changes

2 files changed (+123 additions, -0 deletions)

View changed files

📝 README.md (+2 -0)
➕ examples/guides/openvas-custom-image.md (+121 -0)

📄 Description

Summary

  • add an advanced OpenVAS/GVM custom pentest image guide
  • connect the guide from the README Docker image configuration section
  • frame the workflow as maintainer-recommended experimentation before any first-class API integration

Validation

  • git diff --check
  • verified the README guide link target and worker-node guide link target exist

Refs #69

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/vxcontrol/pentagi/pull/275 **Author:** [@mason5052](https://github.com/mason5052) **Created:** 4/22/2026 **Status:** ✅ Merged **Merged:** 4/28/2026 **Merged by:** [@asdek](https://github.com/asdek) **Base:** `feature/next-release` ← **Head:** `codex/issue-69-openvas-custom-image-guide` --- ### 📝 Commits (2) - [`3e4e800`](https://github.com/vxcontrol/pentagi/commit/3e4e800c4482d943704694e6b59a8d3345b45d9a) docs: add OpenVAS custom image guide - [`fb607a8`](https://github.com/vxcontrol/pentagi/commit/fb607a8bc7dc2fc70d34c9bb7a9379665da80ce9) Merge branch 'feature/next-release' into codex/issue-69-openvas-custom-image-guide ### 📊 Changes **2 files changed** (+123 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+2 -0) ➕ `examples/guides/openvas-custom-image.md` (+121 -0) </details> ### 📄 Description ## Summary - add an advanced OpenVAS/GVM custom pentest image guide - connect the guide from the README Docker image configuration section - frame the workflow as maintainer-recommended experimentation before any first-class API integration ## Validation - `git diff --check` - verified the README guide link target and worker-node guide link target exist Refs #69 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-06 22:10:04 -04:00
yindo closed this issue 2026-06-06 22:10:04 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#288
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?