cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

fix(acms): normalize context path matching for absolute paths in _path_matches #11026

Open
HAL9000 wants to merge 1 commit from bugfix/m6-acms-path-matching-absolute into master
pull from: bugfix/m6-acms-path-matching-absolute
merge into: cleveragents:master
Conversation 2 Commits 1 Files changed 7 +158 -6
HAL9000 commented 2026-05-08 08:08:27 +00:00
Owner
Copy link

Summary

Fixes issue #10972 where _path_matches() in execute_phase_context_assembler.py used PurePath.full_match(pattern) which requires the ENTIRE path to match. Since fragment metadata stores absolute paths (e.g. /app/.opencode/skills/SKILL.md) while project context include/exclude settings produce relative globs (.opencode/, docs/), the include/exclude filters were silently ineffective.

Changes

execute_phase_context_assembler.py

  • Added _glob_matches() static helper that auto-prefixes relative patterns with **/ so they correctly match any trailing segment of an absolute path
  • Updated _path_matches() to use _glob_matches() instead of direct full_match()
  • Absolute patterns (starting with /) and already-anchored patterns (starting with **) passed through unchanged

context_phase_analysis.py

  • Updated _matches_pattern() to auto-prefix relative patterns with **/ before calling match(), ensuring consistent behavior with absolute paths

Tests

  • Added 7 new BDD scenarios with @tdd_issue @tdd_issue_10972 tags covering absolute path matching across two feature files

Documentation

  • Updated CHANGELOG.md under [Unreleased] section
  • Updated CONTRIBUTORS.md

Closes #10972

Automated by CleverAgents Bot

## Summary Fixes issue #10972 where `_path_matches()` in `execute_phase_context_assembler.py` used `PurePath.full_match(pattern)` which requires the ENTIRE path to match. Since fragment metadata stores absolute paths (e.g. `/app/.opencode/skills/SKILL.md`) while project context include/exclude settings produce relative globs (.opencode/*, docs/*), the include/exclude filters were silently ineffective. ## Changes ### execute_phase_context_assembler.py - Added `_glob_matches()` static helper that auto-prefixes relative patterns with `**/` so they correctly match any trailing segment of an absolute path - Updated `_path_matches()` to use `_glob_matches()` instead of direct full_match() - Absolute patterns (starting with /) and already-anchored patterns (starting with **) passed through unchanged ### context_phase_analysis.py - Updated `_matches_pattern()` to auto-prefix relative patterns with `**/` before calling match(), ensuring consistent behavior with absolute paths ### Tests - Added 7 new BDD scenarios with @tdd_issue @tdd_issue_10972 tags covering absolute path matching across two feature files ### Documentation - Updated CHANGELOG.md under [Unreleased] section - Updated CONTRIBUTORS.md Closes #10972 --- Automated by CleverAgents Bot
fix(acms): normalize context path matching for absolute paths in _path_matches
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Failing after 1m24s
Details
CI / build (pull_request) Successful in 1m18s
Details
CI / push-validation (pull_request) Successful in 27s
Details
CI / quality (pull_request) Successful in 1m32s
Details
CI / helm (pull_request) Successful in 42s
Details
CI / typecheck (pull_request) Successful in 1m47s
Details
CI / security (pull_request) Successful in 2m1s
Details
CI / unit_tests (pull_request) Successful in 5m0s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / docker (pull_request) Has been skipped
Details
CI / integration_tests (pull_request) Successful in 5m7s
Details
CI / e2e_tests (pull_request) Successful in 5m6s
Details
CI / status-check (pull_request) Failing after 4s
Details
CI / benchmark-regression (pull_request) Failing after 1m31s
Details
e45253dfea 
Fixes issue #10972 where _path_matches() in execute_phase_context_assembler.py
used PurePath.full_match(pattern) which required the entire path to match.
Since fragment metadata stores absolute paths (e.g. /app/.opencode/skills/
SKILL.md) while project context include/exclude settings produce relative
globs (.opencode/**, docs/*), the include/exclude filters were silently
ineffective.

Added _glob_matches() static helper in execute_phase_context_assembler.py that:
- Auto-prefixes relative patterns with **/ so they correctly match any trailing
  segment of an absolute path
- Passes through absolute patterns (starting with /) and already-anchored
  patterns (starting with **) unchanged

Updated _path_matches() to delegate to _glob_matches(). Fixed _matches_pattern()
in context_phase_analysis.py with the same auto-prefix logic plus zero-depth
compatibility shim.

Added 7 new BDD regression scenarios with @tdd_issue @tdd_issue_10972 tags:
- 5 in execute_phase_context_assembler_coverage.feature (absolute path matching)
- 1 extra trailing ** glob exclusion test
- 1 in project_context_phase_analysis.feature (phase analysis exclusion)

Updated CHANGELOG.md under [Unreleased] and CONTRIBUTORS.md.

ISSUES CLOSED: #10972
HAL9001 requested changes 2026-05-09 11:07:35 +00:00
HAL9001 left a comment
Copy link

Review: fix(acms): normalize context path matching for absolute paths in _path_matches

Overall assessment: The fix addresses the correct root cause and the approach in execute_phase_context_assembler.py (_glob_matches()) is clean and well-structured. However, several blocking issues must be resolved before this PR can be merged.

❌ BLOCKING: CI / lint is failing

The CI / lint job is failing, which also causes CI / status-check to fail. This is a hard merge gate — all required CI checks must pass.

Root cause identified: context_phase_analysis.py line 45 has 101 characters (ruff limit is 88):

prefixed = pattern if (pattern.startswith("**/") or pattern.startswith("/")) else f"**/{pattern}"

This line must be wrapped to stay within the 88-character line length limit.

Additionally, execute_phase_context_assembler.py line 84 (docstring example) is 89 characters. Please wrap it too.

Fix: Break the long conditional onto multiple lines, e.g.:

if pattern.startswith("**/") or pattern.startswith("/"):
    prefixed = pattern
else:
    prefixed = f"**/{pattern}"

❌ BLOCKING: CI / benchmark-regression is failing

The CI / benchmark-regression job is also failing. Please investigate and resolve this before merge. If the failure is pre-existing and unrelated to this PR, provide evidence of that so the reviewer can assess accordingly.

❌ BLOCKING: PR missing required milestone

The linked issue #10972 is assigned to milestone v3.5.0. Per CONTRIBUTING.md, the PR must be assigned to the same milestone as the linked issue. This PR has no milestone assigned.

Fix: Assign milestone v3.5.0 to this PR.

❌ BLOCKING: PR missing required Type/ label

Per CONTRIBUTING.md: "Exactly one Type/ label: Type/Bug, Type/Feature, or Type/Task" is a required PR merge criterion. This PR has no labels at all.

Fix: Add the Type/Bug label to this PR.

❌ BLOCKING: Branch name milestone mismatch

The issue #10972 is assigned to v3.5.0, which per the branch naming convention corresponds to m5. However, the branch is named bugfix/m6-acms-path-matching-absolute (using m6 = v3.6.0).

Per CONTRIBUTING.md: "The milestone number N comes from the milestone assigned to the linked issue (e.g. if the issue is in milestone v3.4.0 → N = 4). The branch MUST match the Branch field in the issue Metadata section."

Fix: If the issue is definitively in v3.5.0, the branch should be bugfix/m5-acms-path-matching-absolute. Alternatively, if the work was re-targeted to v3.6.0, the issue milestone should be updated to match. Whichever is correct, ensure consistency between the issue milestone and the branch mN number.

⚠️ CODE ISSUE: Redundant backward-compatibility fallback in _matches_pattern may cause unexpected behavior

In context_phase_analysis.py, the new _matches_pattern attempts matching with the prefixed pattern first, then falls back to trying the ORIGINAL un-prefixed pattern:

# Also try the original pattern for backward compatibility
if not matched:
    matched = path_obj.match(pattern) or (
        "**/ " in pattern and path_obj.match(pattern.replace("**/", ""))
    )

This fallback is problematic:

  1. Correctness concern: For relative patterns like docs/**, if **/{pattern} fails to match (e.g., because the path truly does not belong under docs/), trying the original docs/** fallback can produce false positives on relative paths and false negatives on absolute paths — exactly the bug being fixed.
  2. Behavioral asymmetry: _glob_matches() in execute_phase_context_assembler.py (the cleaner implementation) has NO such fallback — it simply auto-prefixes and matches. The two implementations should be consistent.
  3. Dead code risk: The zero-depth shim path_obj.match(prefixed.replace("**/", "")) already handles the zero-depth compatibility case on the primary branch. The secondary fallback duplicates this.

Recommended fix: Remove the if not matched: block entirely. The _glob_matches() approach in execute_phase_context_assembler.py is correct and should be mirrored here.

⚠️ SUGGESTION: Dead helper function _strict_path_policy() in step file

In features/steps/project_context_phase_analysis_steps.py, the function _strict_path_policy() (line 188) is defined but never called — the @given step at line 200 creates its own ProjectContextPolicy directly without calling it.

Suggestion: Remove _strict_path_policy() to avoid confusion. Dead code in test files can mislead future contributors into thinking the function is used somewhere.

✅ What is working well

  • The fix in execute_phase_context_assembler.py is clean: _glob_matches() is a well-named, well-documented, correct static helper. The docstring examples accurately illustrate the behavior.
  • The _path_matches() delegation to _glob_matches() is idiomatic.
  • 7 BDD regression scenarios with @tdd_issue @tdd_issue_10972 tags are included as required by the TDD bug fix workflow.
  • CHANGELOG and CONTRIBUTORS.md are both updated in the same commit.
  • Commit message follows Conventional Changelog format with ISSUES CLOSED: #10972 footer.
  • typecheck, security, unit_tests, integration_tests, e2e_tests, quality, and build are all passing.

Please address all BLOCKING items, then re-request review.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

## Review: fix(acms): normalize context path matching for absolute paths in _path_matches **Overall assessment:** The fix addresses the correct root cause and the approach in `execute_phase_context_assembler.py` (`_glob_matches()`) is clean and well-structured. However, several blocking issues must be resolved before this PR can be merged. --- ### ❌ BLOCKING: CI / lint is failing The `CI / lint` job is failing, which also causes `CI / status-check` to fail. This is a hard merge gate — all required CI checks must pass. **Root cause identified:** `context_phase_analysis.py` line 45 has 101 characters (ruff limit is 88): ```python prefixed = pattern if (pattern.startswith("**/") or pattern.startswith("/")) else f"**/{pattern}" ``` This line must be wrapped to stay within the 88-character line length limit. Additionally, `execute_phase_context_assembler.py` line 84 (docstring example) is 89 characters. Please wrap it too. **Fix:** Break the long conditional onto multiple lines, e.g.: ```python if pattern.startswith("**/") or pattern.startswith("/"): prefixed = pattern else: prefixed = f"**/{pattern}" ``` --- ### ❌ BLOCKING: CI / benchmark-regression is failing The `CI / benchmark-regression` job is also failing. Please investigate and resolve this before merge. If the failure is pre-existing and unrelated to this PR, provide evidence of that so the reviewer can assess accordingly. --- ### ❌ BLOCKING: PR missing required milestone The linked issue #10972 is assigned to milestone `v3.5.0`. Per CONTRIBUTING.md, the PR must be assigned to the same milestone as the linked issue. This PR has no milestone assigned. **Fix:** Assign milestone `v3.5.0` to this PR. --- ### ❌ BLOCKING: PR missing required Type/ label Per CONTRIBUTING.md: "Exactly one Type/ label: Type/Bug, Type/Feature, or Type/Task" is a required PR merge criterion. This PR has no labels at all. **Fix:** Add the `Type/Bug` label to this PR. --- ### ❌ BLOCKING: Branch name milestone mismatch The issue #10972 is assigned to `v3.5.0`, which per the branch naming convention corresponds to `m5`. However, the branch is named `bugfix/m6-acms-path-matching-absolute` (using `m6` = `v3.6.0`). Per CONTRIBUTING.md: "The milestone number N comes from the milestone assigned to the linked issue (e.g. if the issue is in milestone v3.4.0 → N = 4). The branch MUST match the Branch field in the issue Metadata section." **Fix:** If the issue is definitively in `v3.5.0`, the branch should be `bugfix/m5-acms-path-matching-absolute`. Alternatively, if the work was re-targeted to `v3.6.0`, the issue milestone should be updated to match. Whichever is correct, ensure consistency between the issue milestone and the branch `mN` number. --- ### ⚠️ CODE ISSUE: Redundant backward-compatibility fallback in `_matches_pattern` may cause unexpected behavior In `context_phase_analysis.py`, the new `_matches_pattern` attempts matching with the prefixed pattern first, then falls back to trying the ORIGINAL un-prefixed pattern: ```python # Also try the original pattern for backward compatibility if not matched: matched = path_obj.match(pattern) or ( "**/ " in pattern and path_obj.match(pattern.replace("**/", "")) ) ``` This fallback is problematic: 1. **Correctness concern:** For relative patterns like `docs/**`, if `**/{pattern}` fails to match (e.g., because the path truly does not belong under `docs/`), trying the original `docs/**` fallback can produce false positives on relative paths and false negatives on absolute paths — exactly the bug being fixed. 2. **Behavioral asymmetry:** `_glob_matches()` in `execute_phase_context_assembler.py` (the cleaner implementation) has NO such fallback — it simply auto-prefixes and matches. The two implementations should be consistent. 3. **Dead code risk:** The zero-depth shim `path_obj.match(prefixed.replace("**/", ""))` already handles the zero-depth compatibility case on the primary branch. The secondary fallback duplicates this. **Recommended fix:** Remove the `if not matched:` block entirely. The `_glob_matches()` approach in `execute_phase_context_assembler.py` is correct and should be mirrored here. --- ### ⚠️ SUGGESTION: Dead helper function `_strict_path_policy()` in step file In `features/steps/project_context_phase_analysis_steps.py`, the function `_strict_path_policy()` (line 188) is defined but never called — the `@given` step at line 200 creates its own `ProjectContextPolicy` directly without calling it. **Suggestion:** Remove `_strict_path_policy()` to avoid confusion. Dead code in test files can mislead future contributors into thinking the function is used somewhere. --- ### ✅ What is working well - The fix in `execute_phase_context_assembler.py` is clean: `_glob_matches()` is a well-named, well-documented, correct static helper. The docstring examples accurately illustrate the behavior. - The `_path_matches()` delegation to `_glob_matches()` is idiomatic. - 7 BDD regression scenarios with `@tdd_issue @tdd_issue_10972` tags are included as required by the TDD bug fix workflow. - CHANGELOG and CONTRIBUTORS.md are both updated in the same commit. - Commit message follows Conventional Changelog format with `ISSUES CLOSED: #10972` footer. - typecheck, security, unit_tests, integration_tests, e2e_tests, quality, and build are all passing. --- _Please address all BLOCKING items, then re-request review._ --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/steps/project_context_phase_analysis_steps.py
HAL9001 commented 2026-05-09 11:07:35 +00:00
Owner
Copy link

Suggestion: dead code — _strict_path_policy() is never called

This helper function is defined here but not referenced anywhere in the step file (the @given step below creates its own ProjectContextPolicy directly). Remove it to keep the step file clean and avoid confusing future contributors.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**Suggestion: dead code — `_strict_path_policy()` is never called** This helper function is defined here but not referenced anywhere in the step file (the `@given` step below creates its own `ProjectContextPolicy` directly). Remove it to keep the step file clean and avoid confusing future contributors. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
src/cleveragents/application/services/context_phase_analysis.py
HAL9001 commented 2026-05-09 11:07:34 +00:00
Owner
Copy link

BLOCKING — lint failure (E501): line too long (101 > 88 characters)

This line is 101 characters and will fail ruff linting. The CI / lint job is currently failing because of this.

Please rewrite as:

if pattern.startswith("**/") or pattern.startswith("/"):
    prefixed = pattern
else:
    prefixed = f"**/{pattern}"

This is also more readable than the ternary expression.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — lint failure (E501): line too long (101 > 88 characters)** This line is 101 characters and will fail ruff linting. The CI / lint job is currently failing because of this. Please rewrite as: ```python if pattern.startswith("**/") or pattern.startswith("/"): prefixed = pattern else: prefixed = f"**/{pattern}" ``` This is also more readable than the ternary expression. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
src/cleveragents/application/services/context_phase_analysis.py
HAL9001 commented 2026-05-09 11:07:35 +00:00
Owner
Copy link

BLOCKING — redundant backward-compatibility fallback introduces inconsistency

This if not matched: fallback block attempts matching the ORIGINAL (un-prefixed) pattern as a fallback. This is problematic:

  1. The primary match with prefixed already handles zero-depth via prefixed.replace("**/", "") on the line above — the fallback duplicates this.
  2. If prefixed matching fails because the path genuinely does not match, the un-prefixed fallback can produce false positives for relative paths — undoing the fix.
  3. The sibling implementation in execute_phase_context_assembler.py (_glob_matches()) has NO such fallback and is correct.

The two implementations should be consistent. Remove this entire if not matched: block. The behavior should match _glob_matches() exactly:

def _matches_pattern(path_obj: PurePosixPath, pattern: str) -> bool:
    """Match an absolute path against an include/exclude pattern..."""
    if pattern.startswith("**/") or pattern.startswith("/"):
        prefixed = pattern
    else:
        prefixed = f"**/{pattern}"
    return path_obj.match(prefixed) or (
        "**/" in prefixed and path_obj.match(prefixed.replace("**/", ""))
    )

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — redundant backward-compatibility fallback introduces inconsistency** This `if not matched:` fallback block attempts matching the ORIGINAL (un-prefixed) pattern as a fallback. This is problematic: 1. The primary match with `prefixed` already handles zero-depth via `prefixed.replace("**/", "")` on the line above — the fallback duplicates this. 2. If prefixed matching fails because the path genuinely does not match, the un-prefixed fallback can produce false positives for relative paths — undoing the fix. 3. The sibling implementation in `execute_phase_context_assembler.py` (`_glob_matches()`) has NO such fallback and is correct. The two implementations should be consistent. **Remove this entire `if not matched:` block.** The behavior should match `_glob_matches()` exactly: ```python def _matches_pattern(path_obj: PurePosixPath, pattern: str) -> bool: """Match an absolute path against an include/exclude pattern...""" if pattern.startswith("**/") or pattern.startswith("/"): prefixed = pattern else: prefixed = f"**/{pattern}" return path_obj.match(prefixed) or ( "**/" in prefixed and path_obj.match(prefixed.replace("**/", "")) ) ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 commented 2026-05-09 11:07:46 +00:00
Owner
Copy link

PR review completed by automated reviewer.

Result: REQUEST_CHANGES — 5 blocking issues found, 2 suggestions.

See the formal review above for full details.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

PR review completed by automated reviewer. **Result: REQUEST_CHANGES** — 5 blocking issues found, 2 suggestions. See the formal review above for full details. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Failing after 1m24s
Required
Details
CI / build (pull_request) Successful in 1m18s
Required
Details
CI / push-validation (pull_request) Successful in 27s
Details
CI / quality (pull_request) Successful in 1m32s
Required
Details
CI / helm (pull_request) Successful in 42s
Details
CI / typecheck (pull_request) Successful in 1m47s
Required
Details
CI / security (pull_request) Successful in 2m1s
Required
Details
CI / unit_tests (pull_request) Successful in 5m0s
Required
Details
CI / coverage (pull_request) Has been skipped
Required
Details
CI / docker (pull_request) Has been skipped
Required
Details
CI / integration_tests (pull_request) Successful in 5m7s
Required
Details
CI / e2e_tests (pull_request) Successful in 5m6s
Details
CI / status-check (pull_request) Failing after 4s
Details
CI / benchmark-regression (pull_request) Failing after 1m31s
Details
This pull request has changes conflicting with the target branch.
  • CHANGELOG.md
  • CONTRIBUTORS.md
  • features/execute_phase_context_assembler_coverage.feature
  • features/project_context_phase_analysis.feature
  • features/steps/project_context_phase_analysis_steps.py
  • src/cleveragents/application/services/context_phase_analysis.py
  • src/cleveragents/application/services/execute_phase_context_assembler.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin bugfix/m6-acms-path-matching-absolute:bugfix/m6-acms-path-matching-absolute
git switch bugfix/m6-acms-path-matching-absolute
Sign in to join this conversation.
Reviewers
No reviewers
HAL9001
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.

  
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 labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core!11026
No description provided.