TEST-INFRA: [ci-pipeline-design] Remove redundant dead_code nox session #1689

Open
opened 2026-04-02 23:30:00 +00:00 by freemo · 2 comments
Owner

Metadata

  • Branch: chore/ci-remove-dead-code-session
  • Commit Message: chore(nox): remove redundant dead_code session superseded by security_scan
  • Milestone: v3.2.0
  • Parent Epic: #1678

Overview

The security_scan nox session already runs vulture for dead code detection, making the separate dead_code session redundant. Removing the dead_code session will simplify noxfile.py and the CI configuration, reducing unnecessary duplication in the quality gate pipeline.

Subtasks

  • Remove the dead_code nox session from noxfile.py.
  • Remove dead_code from the default nox.options.sessions list in noxfile.py.
  • Update any CI workflow references to the dead_code session.
  • Verify vulture continues to run as part of the security_scan session.

Definition of Done

  • The dead_code nox session is fully removed from noxfile.py.
  • The dead_code session is removed from the default sessions list.
  • The CI pipeline continues to run vulture as part of the security_scan session.
  • No references to the dead_code session remain in CI configuration or documentation.
  • All nox stages pass.
  • Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `chore/ci-remove-dead-code-session` - **Commit Message**: `chore(nox): remove redundant dead_code session superseded by security_scan` - **Milestone**: v3.2.0 - **Parent Epic**: #1678 ## Overview The `security_scan` nox session already runs `vulture` for dead code detection, making the separate `dead_code` session redundant. Removing the `dead_code` session will simplify `noxfile.py` and the CI configuration, reducing unnecessary duplication in the quality gate pipeline. ## Subtasks - [ ] Remove the `dead_code` nox session from `noxfile.py`. - [ ] Remove `dead_code` from the default `nox.options.sessions` list in `noxfile.py`. - [ ] Update any CI workflow references to the `dead_code` session. - [ ] Verify `vulture` continues to run as part of the `security_scan` session. ## Definition of Done - [ ] The `dead_code` nox session is fully removed from `noxfile.py`. - [ ] The `dead_code` session is removed from the default sessions list. - [ ] The CI pipeline continues to run `vulture` as part of the `security_scan` session. - [ ] No references to the `dead_code` session remain in CI configuration or documentation. - [ ] All nox stages pass. - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.2.0 milestone 2026-04-02 23:30:33 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • MoSCoW: MoSCoW/Could Have — CI/test infrastructure improvement. Could Have.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Issue triaged by project owner: - **State**: Verified - **MoSCoW**: MoSCoW/Could Have — CI/test infrastructure improvement. Could Have. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Author
Owner

Label compliance fix applied:

  • Added missing labels based on issue content
  • Reason: Per CONTRIBUTING.md, every issue must have exactly one State/*, Type/*, and Priority/* label.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

Label compliance fix applied: - Added missing labels based on issue content - Reason: Per CONTRIBUTING.md, every issue must have exactly one `State/*`, `Type/*`, and `Priority/*` label. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#1689
No description provided.