Skip to content

Rename BASELINE_POLICY to BASELINE_ATTACK_POLICY for clarity#1763

Merged
hannahwestra25 merged 3 commits into
microsoft:mainfrom
hannahwestra25:hannahwestra25/rename-baseline-policy
May 20, 2026
Merged

Rename BASELINE_POLICY to BASELINE_ATTACK_POLICY for clarity#1763
hannahwestra25 merged 3 commits into
microsoft:mainfrom
hannahwestra25:hannahwestra25/rename-baseline-policy

Conversation

@hannahwestra25
Copy link
Copy Markdown
Contributor

Summary

Renames BASELINE_POLICY to BASELINE_ATTACK_POLICY across the codebase for clarity.

Addresses review feedback requesting a more descriptive name. The word 'baseline' is overloaded; adding 'ATTACK' makes it clear this controls inclusion of the baseline attack (PromptSendingAttack) rather than some other baseline concept.

Changes

  • pyrit/scenario/core/scenario.py - class variable + all references in docstrings/logic
  • pyrit/scenario/scenarios/benchmark/adversarial.py - subclass override
  • .github/instructions/scenarios.instructions.md - contributor docs
  • doc/code/scenarios/0_scenarios.py + .ipynb - walkthrough docs
  • 8 test files - assertions and class definitions

Testing

Pure rename; no behavioral changes.

Addresses review feedback from PR microsoft#1760 requesting a more descriptive
name for the class variable that controls baseline attack inclusion.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@hannahwestra25 hannahwestra25 force-pushed the hannahwestra25/rename-baseline-policy branch from 163337a to 2695990 Compare May 20, 2026 18:41
Renames the enum class to match the BASELINE_ATTACK_POLICY attribute.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@hannahwestra25 hannahwestra25 added this pull request to the merge queue May 20, 2026
Merged via the queue into microsoft:main with commit be0baaa May 20, 2026
48 checks passed
@hannahwestra25 hannahwestra25 deleted the hannahwestra25/rename-baseline-policy branch May 20, 2026 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants