cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

fix(ci): resolve lint errors and remove stale tdd_expected_fail tag #5264

Merged
hurui200320 merged 1 commits from fix/broken-ci into master 2026-04-09 04:41:01 +00:00
Conversation 5 Commits 1 Files Changed 2
+154 -108
hurui200320 commented 2026-04-09 04:28:15 +00:00
Member
Copy Link
Copy Source

Summary

The lint and integration_tests CI jobs on master are currently failing. This PR fixes both:

  1. Lint (nox -e lint) — 51 ruff violations in scripts/validate_automation_tracking.py:

    • Sorted imports per isort convention
    • Replaced deprecated typing.List/Dict/Tuple/Optional with builtin equivalents (list, dict, tuple)
    • Removed unused Optional import and unused local variable issues
    • Fixed trailing whitespace, blank-line whitespace, and 6 lines exceeding 88-char limit
    • Replaced dict.keys() with dict in membership tests
    • Added return type annotation to main()

  2. Integration tests (nox -e integration_tests) — 1 failure in robot/coverage_threshold.robot:

    • Removed tdd_expected_fail, tdd_issue, and tdd_issue_4305 tags from the Noxfile Contains Coverage Threshold Constant test
    • The bug this TDD tag tracked (issue #4305) is now fixed — COVERAGE_THRESHOLD = 97 exists in noxfile.py
    • The TDD expected-fail listener was inverting the passing result to a failure

Local verification

  • nox -e lint — All checks passed
  • nox -e integration_tests — 1962 tests, 1962 passed, 0 failed, 0 skipped

Files changed

File Change
scripts/validate_automation_tracking.py Fixed all 51 lint violations
robot/coverage_threshold.robot Removed stale tdd_expected_fail tag

Closes #5266

## Summary The `lint` and `integration_tests` CI jobs on `master` are currently failing. This PR fixes both: 1. **Lint (`nox -e lint`)** — 51 ruff violations in `scripts/validate_automation_tracking.py`: - Sorted imports per isort convention - Replaced deprecated `typing.List`/`Dict`/`Tuple`/`Optional` with builtin equivalents (`list`, `dict`, `tuple`) - Removed unused `Optional` import and unused local variable `issues` - Fixed trailing whitespace, blank-line whitespace, and 6 lines exceeding 88-char limit - Replaced `dict.keys()` with `dict` in membership tests - Added return type annotation to `main()` 2. **Integration tests (`nox -e integration_tests`)** — 1 failure in `robot/coverage_threshold.robot`: - Removed `tdd_expected_fail`, `tdd_issue`, and `tdd_issue_4305` tags from the `Noxfile Contains Coverage Threshold Constant` test - The bug this TDD tag tracked (issue #4305) is now fixed — `COVERAGE_THRESHOLD = 97` exists in `noxfile.py` - The TDD expected-fail listener was inverting the passing result to a failure ### Local verification - `nox -e lint` — All checks passed - `nox -e integration_tests` — 1962 tests, 1962 passed, 0 failed, 0 skipped ### Files changed | File | Change | |------|--------| | `scripts/validate_automation_tracking.py` | Fixed all 51 lint violations | | `robot/coverage_threshold.robot` | Removed stale `tdd_expected_fail` tag | Closes #5266
hurui200320 added 1 commit 2026-04-09 04:28:15 +00:00
fix(ci): resolve lint errors and remove stale tdd_expected_fail tag
CI / lint (pull_request) Successful in 40s
Details
CI / quality (pull_request) Successful in 43s
Details
CI / security (pull_request) Successful in 49s
Details
CI / typecheck (pull_request) Successful in 51s
Details
CI / push-validation (pull_request) Successful in 20s
Details
CI / build (pull_request) Successful in 31s
Details
CI / helm (pull_request) Successful in 1m0s
Details
CI / e2e_tests (pull_request) Successful in 3m13s
Details
CI / integration_tests (pull_request) Successful in 6m27s
Details
CI / unit_tests (pull_request) Successful in 7m32s
Details
CI / docker (pull_request) Successful in 1m33s
Details
CI / coverage (pull_request) Successful in 10m32s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 57m26s
Details
77c29238c4 
Fixed 51 ruff lint violations in scripts/validate_automation_tracking.py:
- Sorted imports per isort convention
- Replaced deprecated typing.List/Dict/Tuple/Optional with builtin equivalents
- Removed unused Optional import and unused local variable
- Fixed trailing whitespace, blank-line whitespace, and line-too-long errors
- Replaced dict.keys() with dict in membership tests

Removed tdd_expected_fail tag from Robot.Coverage Threshold test
'Noxfile Contains Coverage Threshold Constant' (issue #4305) because
the bug it tracked is now fixed (COVERAGE_THRESHOLD = 97 exists in
noxfile.py). The TDD listener was inverting the passing result to a
failure.
hurui200320 self-assigned this 2026-04-09 04:31:40 +00:00
hurui200320 commented 2026-04-09 04:33:14 +00:00
Author
Member
Copy Link
Copy Source

@HAL9000 please review this PR asap since it tries to get the CI back into a working state.

@HAL9000 please review this PR asap since it tries to get the CI back into a working state.
HAL9000 reviewed 2026-04-09 04:35:31 +00:00
HAL9000 left a comment
Owner
Copy Link
Copy Source

PR Review — fix(ci): resolve lint errors and remove stale tdd_expected_fail tag

This PR addresses the two active master CI failures. The changes are correct and well-scoped.

Lint Fix (scripts/validate_automation_tracking.py)

The 51 ruff violations are standard modernization fixes:

  • Import sorting and removal of unused Optional import
  • Migration from deprecated typing.List/Dict/Tuple/Optional to builtin equivalents — correct per Python 3.9+ conventions
  • Line length, whitespace, and dict.keys() membership test fixes

These are all mechanical correctness fixes with no behavioral change. The approach is correct.

TDD Tag Removal (robot/coverage_threshold.robot)

Removing tdd_expected_fail, tdd_issue, and tdd_issue_4305 from the Noxfile Contains Coverage Threshold Constant test is the correct action. Per our TDD workflow:

  • tdd_expected_fail must be removed in the same commit that fixes the underlying bug
  • Issue #4305 is resolved — COVERAGE_THRESHOLD = 97 exists in noxfile.py
  • The tag was inverting a passing test to a failure, which is the expected behavior while the bug existed

Removing all three TDD tags together is correct procedure.

Assessment

The PR is well-formed, the changes are correct, and local verification was performed (1962 tests, 0 failures). CI checks are currently pending.

Recommendation: Merge once CI passes.

Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: human-liaison

## PR Review — fix(ci): resolve lint errors and remove stale tdd_expected_fail tag This PR addresses the two active master CI failures. The changes are correct and well-scoped. ### Lint Fix (`scripts/validate_automation_tracking.py`) The 51 ruff violations are standard modernization fixes: - Import sorting and removal of unused `Optional` import - Migration from deprecated `typing.List`/`Dict`/`Tuple`/`Optional` to builtin equivalents — correct per Python 3.9+ conventions - Line length, whitespace, and `dict.keys()` membership test fixes These are all mechanical correctness fixes with no behavioral change. The approach is correct. ### TDD Tag Removal (`robot/coverage_threshold.robot`) Removing `tdd_expected_fail`, `tdd_issue`, and `tdd_issue_4305` from the `Noxfile Contains Coverage Threshold Constant` test is the correct action. Per our TDD workflow: - `tdd_expected_fail` must be removed in the same commit that fixes the underlying bug - Issue #4305 is resolved — `COVERAGE_THRESHOLD = 97` exists in `noxfile.py` - The tag was inverting a passing test to a failure, which is the expected behavior while the bug existed Removing all three TDD tags together is correct procedure. ### Assessment The PR is well-formed, the changes are correct, and local verification was performed (1962 tests, 0 failures). CI checks are currently pending. **Recommendation**: Merge once CI passes. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: human-liaison
HAL9000 added the
Priority
Medium
State
In Review
Type
Bug
 labels 2026-04-09 04:35:57 +00:00
HAL9000 requested changes 2026-04-09 04:37:28 +00:00
HAL9000 left a comment
Owner
Copy Link
Copy Source

Review Summary

Reviewed PR with focus on specification-compliance, requirements-coverage, and behavior-correctness.

The lint fixes in scripts/validate_automation_tracking.py are correct and well-executed. However, there is a critical TDD tag violation in robot/coverage_threshold.robot, plus two missing required PR metadata fields.

❌ Required Changes

1. [CRITICAL] TDD Regression Markers Incorrectly Removed

Location: robot/coverage_threshold.robot — Noxfile Contains Coverage Threshold Constant test

Issue: The PR removed ALL three TDD tags from this test, but only tdd_expected_fail should be removed. The tdd_issue and tdd_issue_4305 tags are permanent regression markers and must remain.

Master (before):

Noxfile Contains Coverage Threshold Constant
    [Documentation]    Verify COVERAGE_THRESHOLD = 97 is defined in noxfile.py
    [Tags]    coverage    config    tdd_issue    tdd_issue_4305    tdd_expected_fail

This PR (after):

Noxfile Contains Coverage Threshold Constant
    [Documentation]    Verify COVERAGE_THRESHOLD = 97 is defined in noxfile.py
    [Tags]    coverage    config

Required (correct):

Noxfile Contains Coverage Threshold Constant
    [Documentation]    Verify COVERAGE_THRESHOLD = 97 is defined in noxfile.py
    [Tags]    coverage    config    tdd_issue    tdd_issue_4305

Why this matters: Per CONTRIBUTING.md (Bug Fix Workflow / TDD Issue Test Tags):

@tdd_issue and @tdd_issue_<N> should remain (permanent regression markers)
@tdd_expected_fail MUST be removed for the bug being fixed

The tdd_issue and tdd_issue_4305 tags serve as permanent regression guards. If COVERAGE_THRESHOLD = 97 is ever removed from noxfile.py in the future, these tags ensure the test is still identifiable as a TDD regression test for issue #4305. Removing them silently strips that traceability and regression protection.

2. [REQUIRED] Missing Milestone on PR

Reference: CONTRIBUTING.md — Pull Request Process, item 11:

"Every PR must be assigned to the same milestone as its linked issues."

Issue #5266 is assigned to milestone v3.2.0. This PR has no milestone assigned. Please assign milestone v3.2.0 to this PR.

3. [REQUIRED] Missing Type/ Label on PR

Reference: CONTRIBUTING.md — Pull Request Process, item 12:

"Every PR must carry exactly one Type/ label that matches the nature of the change."

This PR has no labels at all. Given this is a bug/CI fix, the appropriate label is Type/Bug. Please apply it.

⚠️ Concern (Non-blocking but should be addressed)

Issue #4305 Still Open

The PR description states: "The bug this TDD tag tracked (issue #4305) is now fixed — COVERAGE_THRESHOLD = 97 exists in noxfile.py."

However, issue #4305 (fix(integration): coverage_threshold — 1 failing test(s)) is still open with State/Verified. If the underlying fix is already merged to master, issue #4305 should be closed. Consider either:

  • Adding Closes #4305 to this PR's description (if this PR is the appropriate place to close it), or
  • Closing issue #4305 separately with a comment explaining it was resolved by the prior commit that added COVERAGE_THRESHOLD = 97 to noxfile.py

✅ What's Good

  • Lint fixes are correct and complete: All 51 ruff violations in scripts/validate_automation_tracking.py are properly addressed:
    • Deprecated typing.List/Dict/Tuple/Optional replaced with builtin equivalents (list, dict, tuple) ✅
    • Unused Optional import removed ✅
    • Return type annotation added to main() -> int ✅
    • Import ordering fixed ✅
    • Line length, trailing whitespace, and blank-line whitespace corrected ✅
    • dict.keys() membership test replaced with dict directly ✅
  • No # type: ignore suppressions ✅
  • File is under 500 lines (7,653 bytes ≈ ~200 lines) ✅
  • Commit message format follows Conventional Changelog: fix(ci): resolve lint errors and remove stale tdd_expected_fail tag ✅
  • Closing keyword present: Closes #5266 ✅
  • PR description is detailed and explains both changes clearly ✅
  • The tdd_expected_fail removal itself is correct — COVERAGE_THRESHOLD = 97 is confirmed present in noxfile.py on master, so the TDD listener was correctly inverting a passing test to a failure ✅

Summary of Required Changes

# Severity Location Action Required
1 🔴 Critical robot/coverage_threshold.robot Restore tdd_issue and tdd_issue_4305 tags; keep only tdd_expected_fail removed
2 🔴 Required PR metadata Assign milestone v3.2.0
3 🔴 Required PR metadata Apply Type/Bug label
4 🟡 Concern Issue #4305 Close issue #4305 or explain why it remains open

Decision: REQUEST CHANGES 🔄

The lint fixes are solid and the CI motivation is urgent — but the TDD tag removal is incorrect and would silently eliminate permanent regression protection for issue #4305. The fix is a one-line change: restore tdd_issue and tdd_issue_4305 to the Noxfile Contains Coverage Threshold Constant test while keeping tdd_expected_fail removed.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-self-reviewer

## Review Summary Reviewed PR with focus on **specification-compliance**, **requirements-coverage**, and **behavior-correctness**. The lint fixes in `scripts/validate_automation_tracking.py` are correct and well-executed. However, there is a **critical TDD tag violation** in `robot/coverage_threshold.robot`, plus two missing required PR metadata fields. --- ### ❌ Required Changes #### 1. [CRITICAL] TDD Regression Markers Incorrectly Removed **Location:** `robot/coverage_threshold.robot` — `Noxfile Contains Coverage Threshold Constant` test **Issue:** The PR removed ALL three TDD tags from this test, but only `tdd_expected_fail` should be removed. The `tdd_issue` and `tdd_issue_4305` tags are **permanent regression markers** and must remain. **Master (before):** ```robot Noxfile Contains Coverage Threshold Constant [Documentation] Verify COVERAGE_THRESHOLD = 97 is defined in noxfile.py [Tags] coverage config tdd_issue tdd_issue_4305 tdd_expected_fail ``` **This PR (after):** ```robot Noxfile Contains Coverage Threshold Constant [Documentation] Verify COVERAGE_THRESHOLD = 97 is defined in noxfile.py [Tags] coverage config ``` **Required (correct):** ```robot Noxfile Contains Coverage Threshold Constant [Documentation] Verify COVERAGE_THRESHOLD = 97 is defined in noxfile.py [Tags] coverage config tdd_issue tdd_issue_4305 ``` **Why this matters:** Per CONTRIBUTING.md (Bug Fix Workflow / TDD Issue Test Tags): > `@tdd_issue` and `@tdd_issue_<N>` should remain (permanent regression markers) > `@tdd_expected_fail` MUST be removed for the bug being fixed The `tdd_issue` and `tdd_issue_4305` tags serve as permanent regression guards. If `COVERAGE_THRESHOLD = 97` is ever removed from `noxfile.py` in the future, these tags ensure the test is still identifiable as a TDD regression test for issue #4305. Removing them silently strips that traceability and regression protection. --- #### 2. [REQUIRED] Missing Milestone on PR **Reference:** CONTRIBUTING.md — Pull Request Process, item 11: > "Every PR must be assigned to the same milestone as its linked issues." Issue #5266 is assigned to milestone **v3.2.0**. This PR has **no milestone** assigned. Please assign milestone v3.2.0 to this PR. --- #### 3. [REQUIRED] Missing Type/ Label on PR **Reference:** CONTRIBUTING.md — Pull Request Process, item 12: > "Every PR must carry exactly one `Type/` label that matches the nature of the change." This PR has **no labels at all**. Given this is a bug/CI fix, the appropriate label is `Type/Bug`. Please apply it. --- ### ⚠️ Concern (Non-blocking but should be addressed) #### Issue #4305 Still Open The PR description states: *"The bug this TDD tag tracked (issue #4305) is now fixed — `COVERAGE_THRESHOLD = 97` exists in `noxfile.py`."* However, issue #4305 (`fix(integration): coverage_threshold — 1 failing test(s)`) is still **open** with `State/Verified`. If the underlying fix is already merged to master, issue #4305 should be closed. Consider either: - Adding `Closes #4305` to this PR's description (if this PR is the appropriate place to close it), or - Closing issue #4305 separately with a comment explaining it was resolved by the prior commit that added `COVERAGE_THRESHOLD = 97` to `noxfile.py` --- ### ✅ What's Good - **Lint fixes are correct and complete:** All 51 ruff violations in `scripts/validate_automation_tracking.py` are properly addressed: - Deprecated `typing.List/Dict/Tuple/Optional` replaced with builtin equivalents (`list`, `dict`, `tuple`) ✅ - Unused `Optional` import removed ✅ - Return type annotation added to `main() -> int` ✅ - Import ordering fixed ✅ - Line length, trailing whitespace, and blank-line whitespace corrected ✅ - `dict.keys()` membership test replaced with `dict` directly ✅ - **No `# type: ignore` suppressions** ✅ - **File is under 500 lines** (7,653 bytes ≈ ~200 lines) ✅ - **Commit message format** follows Conventional Changelog: `fix(ci): resolve lint errors and remove stale tdd_expected_fail tag` ✅ - **Closing keyword** present: `Closes #5266` ✅ - **PR description** is detailed and explains both changes clearly ✅ - **The `tdd_expected_fail` removal itself is correct** — `COVERAGE_THRESHOLD = 97` is confirmed present in `noxfile.py` on master, so the TDD listener was correctly inverting a passing test to a failure ✅ --- ### Summary of Required Changes | # | Severity | Location | Action Required | |---|----------|----------|-----------------| | 1 | 🔴 Critical | `robot/coverage_threshold.robot` | Restore `tdd_issue` and `tdd_issue_4305` tags; keep only `tdd_expected_fail` removed | | 2 | 🔴 Required | PR metadata | Assign milestone v3.2.0 | | 3 | 🔴 Required | PR metadata | Apply `Type/Bug` label | | 4 | 🟡 Concern | Issue #4305 | Close issue #4305 or explain why it remains open | **Decision: REQUEST CHANGES** 🔄 The lint fixes are solid and the CI motivation is urgent — but the TDD tag removal is incorrect and would silently eliminate permanent regression protection for issue #4305. The fix is a one-line change: restore `tdd_issue` and `tdd_issue_4305` to the `Noxfile Contains Coverage Threshold Constant` test while keeping `tdd_expected_fail` removed. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: pr-self-reviewer
robot/coverage_threshold.robot
@@ -9,7 +9,7 @@ Suite Teardown Cleanup Test Environment
*** Test Cases ***
Noxfile Contains Coverage Threshold Constant
HAL9000 commented 2026-04-09 04:37:28 +00:00
Owner
Copy Link
Copy Source

TDD Regression Markers Incorrectly Removed

Only tdd_expected_fail should be removed when a bug is fixed. The tdd_issue and tdd_issue_4305 tags are permanent regression markers and must remain.

Current (incorrect):

[Tags]    coverage    config

Required (correct):

[Tags]    coverage    config    tdd_issue    tdd_issue_4305

Per CONTRIBUTING.md TDD Issue Test Tags:

@tdd_issue and @tdd_issue_<N> should remain (permanent regression markers)
@tdd_expected_fail MUST be removed for the bug being fixed

**TDD Regression Markers Incorrectly Removed** Only `tdd_expected_fail` should be removed when a bug is fixed. The `tdd_issue` and `tdd_issue_4305` tags are **permanent regression markers** and must remain. Current (incorrect): ```robot [Tags] coverage config ``` Required (correct): ```robot [Tags] coverage config tdd_issue tdd_issue_4305 ``` Per CONTRIBUTING.md TDD Issue Test Tags: > `@tdd_issue` and `@tdd_issue_<N>` should remain (permanent regression markers) > `@tdd_expected_fail` MUST be removed for the bug being fixed
hurui200320 added this to the v3.2.0 milestone 2026-04-09 04:39:13 +00:00
hurui200320 merged commit 0bd8fbb296 into master 2026-04-09 04:41:01 +00:00
hurui200320 deleted branch fix/broken-ci 2026-04-09 04:41:01 +00:00
hurui200320 commented 2026-04-09 04:43:39 +00:00
Author
Member
Copy Link
Copy Source

For the record, I'm merging this PR anyway since:

  • The config validation is not really a TDD bug, Jeff (freemo) temporarily lower the coverage to 50% to fix CI, but then switched back to 97% percent. This is not a bug, more like a config issue
  • Missing labels are fixed
  • #4305 has been closed

I see no harm on merging this, instead, merging this should bring the CI back to a working state so it will unblock other issues and PRs.

For the record, I'm merging this PR anyway since: + The config validation is not really a TDD bug, Jeff (freemo) temporarily lower the coverage to 50% to fix CI, but then switched back to 97% percent. This is not a bug, more like a config issue + Missing labels are fixed + #4305 has been closed I see no harm on merging this, instead, merging this should bring the CI back to a working state so it will unblock other issues and PRs.
HAL9000 commented 2026-04-09 04:44:20 +00:00
Owner
Copy Link
Copy Source

PR merged. The master CI fix is now in. Thank you @hurui200320 for the clear explanation and for resolving this promptly.

The reasoning is sound:

  • The coverage threshold change was a temporary config adjustment by @freemo, not a persistent bug
  • Issue #4305 was already closed
  • The stale tdd_expected_fail tag was the only remaining artifact

Master CI should now pass on the next run.

Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: human-liaison

PR merged. The master CI fix is now in. Thank you @hurui200320 for the clear explanation and for resolving this promptly. The reasoning is sound: - The coverage threshold change was a temporary config adjustment by @freemo, not a persistent bug - Issue #4305 was already closed - The stale `tdd_expected_fail` tag was the only remaining artifact Master CI should now pass on the next run. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: human-liaison
Sign in to join this conversation.
Reviewers
No Reviewers
HAL9000
Labels
Clear labels
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
 controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
 overdue
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
 auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
 auto/claimed-implementer
Currently being processed by an implementer worker.
 auto/claimed-merge
Currently being processed by the merge driver.
 auto/claimed-reviewer
Currently being processed by a reviewer worker.
 auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
 auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
 auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
 auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
 Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.
 auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.
 auto/needs-implementer
Failing CI needs implementer attention.
 auto/postmortem
Documenting a driver incident or rollback.
 auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
 auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
 auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
 auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
 auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
 auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
 Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
Priority
Medium
State
In Review
Type
Bug
Milestone
No items
No Milestone v3.2.0
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees hurui200320
2 Participants
Notifications
Due Date
No due date set.
Blocks
#5266 fix(ci): resolve broken lint and integration_tests on master
cleveragents/cleveragents-core
Reference: cleveragents/cleveragents-core#5264
Delete Branch "fix/broken-ci"

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?