From 1e7891747d4ff8b4462f75de875b30b650177045 Mon Sep 17 00:00:00 2001 From: Veronica Valeros Date: Thu, 12 Mar 2026 10:00:01 +0100 Subject: [PATCH 01/11] chore: sync .github/CONTRIBUTING.md --- .github/CONTRIBUTING.md | 43 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 .github/CONTRIBUTING.md diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md new file mode 100644 index 00000000..8a228e50 --- /dev/null +++ b/.github/CONTRIBUTING.md @@ -0,0 +1,43 @@ +# Contributing + +All contributions are welcomed, thank you for taking the time to contribute to this project! + +## How can you contribute? + +* Report bugs +* Suggest features and ideas +* Pull requests with a solved GitHub issue and new feature +* Pull request with a new content. + +## Persistent Git Branches + +The following git branches permanent in the repository: + +- `main`: contains the stable version of the repository. All new features should be based on this branch. + +## Naming Git branches for Pull Requests + +To keep the Git history clean and facilitate the revision of contributions we +ask all branches to follow concise namings. These are the branch-naming patterns +to follow when contributing: + +- name-bugfix-<>: pull request branch, contains one bugfix, +- name-docs-<>: pull request branch, contains documentation work, +- name-enhance-<>: pull request branch, contains one enhancement (not a new feature, but improvement nonetheless) +- name-feature-<>: pull request branch, contains a new feature, +- name-refactor-<>: pull request branch, contains code refactoring, + +## What branch should you base your contribution? + +As a general rule, base your contribution on the `main` branch. + +## Creating a pull request + +Commits: +- Commits should do one thing. Keep it simple. +- Commit messages should be easily readable, imperative style ("Fix memory leak in...", not "FixES mem...") + +Pull Requests: +- If you have developed multiple features and/or bugfixes, create separate + branches for each one of them, and request merges for each branch; +- The cleaner you code/change/changeset is, the faster it will be merged. From 8da6b7e796ca175fdeb0b51821fee3f403529291 Mon Sep 17 00:00:00 2001 From: Veronica Valeros Date: Thu, 12 Mar 2026 10:00:03 +0100 Subject: [PATCH 02/11] chore: sync .github/SECURITY.md --- .github/SECURITY.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 .github/SECURITY.md diff --git a/.github/SECURITY.md b/.github/SECURITY.md new file mode 100644 index 00000000..f6309b7c --- /dev/null +++ b/.github/SECURITY.md @@ -0,0 +1,13 @@ +# Security Policy + +## Reporting a Vulnerability + +Report security vulnerabilities to stratosphere+[repository_name]@aic.fel.cvut.cz. We are a small team. We will acknowledge your email as soon as we can. Report security vulnerabilities in third-party modules to the person or +team maintaining the module. + +## Disclosure Policy + +When our team receives a security bug report, we will take the following steps: + + * Confirm the problem and determine the impact. + * Prepare a fix to the latest current version. From 82fcf1d678981012fca1f51eedd7b6afed296a2e Mon Sep 17 00:00:00 2001 From: Veronica Valeros Date: Thu, 12 Mar 2026 10:00:04 +0100 Subject: [PATCH 03/11] chore: sync .github/CODE_OF_CONDUCT.md --- .github/CODE_OF_CONDUCT.md | 128 +++++++++++++++++++++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 .github/CODE_OF_CONDUCT.md diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md new file mode 100644 index 00000000..ac2264fe --- /dev/null +++ b/.github/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible disability, ethnicity, sex characteristics, gender +identity and expression, level of experience, education, socio-economic status, +nationality, personal appearance, race, religion, or sexual identity +and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +* Demonstrating empathy and kindness toward other people +* Being respectful of differing opinions, viewpoints, and experiences +* Giving and gracefully accepting constructive feedback +* Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +* Focusing on what is best not just for us as individuals, but for the + overall community + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery, and sexual attention or + advances of any kind +* Trolling, insulting or derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or email + address, without their explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders have the right and responsibility to remove, edit, or reject +comments, commits, code, wiki edits, issues, and other contributions that are +not aligned to this Code of Conduct, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +stratosphere@aic.fel.cvut.cz. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series +of actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or +permanent ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within +the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.0, available at +https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct +enforcement ladder](https://github.com/mozilla/diversity). + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. From e0f3fd9a11af810590c52d12e7d703287c576f1e Mon Sep 17 00:00:00 2001 From: Veronica Valeros Date: Thu, 12 Mar 2026 10:00:06 +0100 Subject: [PATCH 04/11] chore: sync .github/pull_request_template.md --- .github/pull_request_template.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 .github/pull_request_template.md diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 00000000..386955b9 --- /dev/null +++ b/.github/pull_request_template.md @@ -0,0 +1,30 @@ +# Description + +Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. + +Fixes # (issue) + +## Type of change + +Please delete options that are not relevant. + +- [ ] Bug fix (non-breaking change which fixes an issue) +- [ ] New feature (non-breaking change which adds functionality) +- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) +- [ ] This change requires a documentation update + +# How Has This Been Tested? + +Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration + +- [ ] Test A +- [ ] Test B + + +# Checklist: + +- [ ] My code follows the style guidelines of this project +- [ ] I have performed a self-review of my code +- [ ] I have commented my code, particularly in hard-to-understand areas +- [ ] I have made corresponding changes to the documentation +- [ ] My changes generate no new warnings From f0a64a26690cbe240a45984fc4926d48df42e99a Mon Sep 17 00:00:00 2001 From: Veronica Valeros Date: Thu, 12 Mar 2026 10:00:07 +0100 Subject: [PATCH 05/11] chore: sync .github/ISSUE_TEMPLATE/feature_request.md --- .github/ISSUE_TEMPLATE/feature_request.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 00000000..835cc937 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,18 @@ +--- +name: Feature request +about: Suggest an idea for this project +title: "[FEAT]" +labels: enhancement +--- + +**Is your feature request related to a problem? Please describe.** +A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] + +**Describe the solution you'd like** +A clear and concise description of what you want to happen. + +**Describe alternatives you've considered** +A clear and concise description of any alternative solutions or features you've considered. + +**Additional context** +Add any other context or screenshots about the feature request here. From 75308e91d262d12f2c2ccb2508601b9e15195723 Mon Sep 17 00:00:00 2001 From: Ondrej Lukas Date: Mon, 16 Mar 2026 11:57:16 +0100 Subject: [PATCH 06/11] Updated PR template --- .github/pull_request_template.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 386955b9..2fccac77 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -3,7 +3,6 @@ Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. Fixes # (issue) - ## Type of change Please delete options that are not relevant. @@ -17,14 +16,11 @@ Please delete options that are not relevant. Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration -- [ ] Test A -- [ ] Test B - # Checklist: - - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation -- [ ] My changes generate no new warnings +- [ ] I have run local pytest +- [ ] I have run local ruff check \ No newline at end of file From b888178f78619f2de7f09907032d0075b6853ea7 Mon Sep 17 00:00:00 2001 From: Ondrej Lukas Date: Mon, 16 Mar 2026 12:00:30 +0100 Subject: [PATCH 07/11] Add more checklits to testing --- .github/pull_request_template.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 2fccac77..9dc5e9f5 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -16,6 +16,11 @@ Please delete options that are not relevant. Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration +- [ ] Manual testing (local run with NetSecGame) +- [ ] Manual testing (local run with WhiteBoxNetSecGame) +- [ ] Local docker run with NetSecGame +- [ ] Local docker run with WhiteBoxNetSecGame + # Checklist: - [ ] My code follows the style guidelines of this project From 9fbc7de40c9dc7a21ce64d41c42d41cf1c1b7239 Mon Sep 17 00:00:00 2001 From: Ondrej Lukas Date: Mon, 16 Mar 2026 12:03:23 +0100 Subject: [PATCH 08/11] Adapt contributation guideline --- .github/CONTRIBUTING.md | 2 +- NetSecGameAgents | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 8a228e50..8c72f8f3 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -14,6 +14,7 @@ All contributions are welcomed, thank you for taking the time to contribute to t The following git branches permanent in the repository: - `main`: contains the stable version of the repository. All new features should be based on this branch. +- `aidojo-stable`: contains the stable version of the repository for AI Dojo Project. ## Naming Git branches for Pull Requests @@ -23,7 +24,6 @@ to follow when contributing: - name-bugfix-<>: pull request branch, contains one bugfix, - name-docs-<>: pull request branch, contains documentation work, -- name-enhance-<>: pull request branch, contains one enhancement (not a new feature, but improvement nonetheless) - name-feature-<>: pull request branch, contains a new feature, - name-refactor-<>: pull request branch, contains code refactoring, diff --git a/NetSecGameAgents b/NetSecGameAgents index cb7a74f8..7dcd242c 160000 --- a/NetSecGameAgents +++ b/NetSecGameAgents @@ -1 +1 @@ -Subproject commit cb7a74f8c6a64ac9cbf2df0a5acfff7b73b980aa +Subproject commit 7dcd242cc9555cf3e0f68ad4176f852cd578f4c0 From 1ce1676ac0f6e9ae81409aa3d316fcbc54562a92 Mon Sep 17 00:00:00 2001 From: Ondrej Lukas Date: Mon, 16 Mar 2026 12:08:25 +0100 Subject: [PATCH 09/11] unify title templates --- .github/ISSUE_TEMPLATE/bug_report.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index 1f2e6461..1283db12 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -1,6 +1,6 @@ name: 🐛 Bug Report description: File a bug report to help us squash errors. -title: "[Bug]: " +title: "[BUG]: " labels: ["bug"] assignees: [ondrej-lukas] From 1d8ca4a5190464eef36fa5b96a597d0ef307b75f Mon Sep 17 00:00:00 2001 From: Ondrej Lukas Date: Mon, 16 Mar 2026 12:09:40 +0100 Subject: [PATCH 10/11] use yaml form of the feature request --- .github/ISSUE_TEMPLATE/feature_request.md | 18 ----------- .github/ISSUE_TEMPLATE/feature_request.yml | 37 ++++++++++++++++++++++ 2 files changed, 37 insertions(+), 18 deletions(-) delete mode 100644 .github/ISSUE_TEMPLATE/feature_request.md create mode 100644 .github/ISSUE_TEMPLATE/feature_request.yml diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md deleted file mode 100644 index 835cc937..00000000 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -name: Feature request -about: Suggest an idea for this project -title: "[FEAT]" -labels: enhancement ---- - -**Is your feature request related to a problem? Please describe.** -A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] - -**Describe the solution you'd like** -A clear and concise description of what you want to happen. - -**Describe alternatives you've considered** -A clear and concise description of any alternative solutions or features you've considered. - -**Additional context** -Add any other context or screenshots about the feature request here. diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml new file mode 100644 index 00000000..338b2795 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -0,0 +1,37 @@ +name: Feature request +description: Suggest an idea for this project +title: "[FEAT] " +labels: ["enhancement"] +assignees: [ondrej-lukas] +body: + - type: textarea + id: problem + attributes: + label: Is your feature request related to a problem? Please describe. + description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] + validations: + required: true + + - type: textarea + id: solution + attributes: + label: Suggested solution + description: A clear and concise description of what you want to happen. + validations: + required: true + + - type: textarea + id: alternatives + attributes: + label: Alternatives considered + description: A clear and concise description of any alternative solutions or features you've considered. + validations: + required: false + + - type: textarea + id: context + attributes: + label: Additional context + description: Add any other context or screenshots about the feature request here. + validations: + required: false \ No newline at end of file From 9e6b203b6b9cc84e246a3f02c37bbff55b0ca7c9 Mon Sep 17 00:00:00 2001 From: Ondrej Lukas Date: Mon, 16 Mar 2026 12:10:39 +0100 Subject: [PATCH 11/11] Use correct email address --- .github/SECURITY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/SECURITY.md b/.github/SECURITY.md index f6309b7c..95a7318f 100644 --- a/.github/SECURITY.md +++ b/.github/SECURITY.md @@ -2,7 +2,7 @@ ## Reporting a Vulnerability -Report security vulnerabilities to stratosphere+[repository_name]@aic.fel.cvut.cz. We are a small team. We will acknowledge your email as soon as we can. Report security vulnerabilities in third-party modules to the person or +Report security vulnerabilities to stratosphere@aic.fel.cvut.cz. We are a small team. We will acknowledge your email as soon as we can. Report security vulnerabilities in third-party modules to the person or team maintaining the module. ## Disclosure Policy