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

fix(providers): add ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER #11110

Closed
HAL9000 wants to merge 1 commit from fix/gemini-fallback-order into master
pull from: fix/gemini-fallback-order
merge into: cleveragents:master
Conversation 3 Commits 1 Files changed 2 +2 -1
HAL9000 commented 2026-05-11 01:22:56 +00:00
Owner
Copy link

This PR adds ProviderType.GEMINI to the fallback order list in the provider registry.

The change ensures Gemini providers are properly included when falling back through available AI providers. When only GEMINI_API_KEY is set, get_default_provider_type() now correctly returns ProviderType.GEMINI instead of None.

Changes:

  • Added ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER after ProviderType.GOOGLE
  • Removed @tdd_expected_fail tag from the TDD scenario since the fix is applied
This PR adds `ProviderType.GEMINI` to the fallback order list in the provider registry. The change ensures Gemini providers are properly included when falling back through available AI providers. When only `GEMINI_API_KEY` is set, `get_default_provider_type()` now correctly returns `ProviderType.GEMINI` instead of `None`. **Changes:** - Added `ProviderType.GEMINI` to `ProviderRegistry.FALLBACK_ORDER` after `ProviderType.GOOGLE` - Removed `@tdd_expected_fail` tag from the TDD scenario since the fix is applied
fix(providers): add ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 52s
Details
CI / helm (pull_request) Successful in 56s
Details
CI / build (pull_request) Successful in 1m13s
Details
CI / benchmark-regression (pull_request) Failing after 1m41s
Details
CI / quality (pull_request) Successful in 1m51s
Details
CI / lint (pull_request) Successful in 1m55s
Details
CI / typecheck (pull_request) Successful in 2m2s
Details
CI / security (pull_request) Successful in 2m1s
Details
CI / integration_tests (pull_request) Successful in 4m0s
Details
CI / e2e_tests (pull_request) Successful in 5m10s
Details
CI / unit_tests (pull_request) Successful in 5m25s
Details
CI / docker (pull_request) Successful in 2m0s
Details
CI / coverage (pull_request) Successful in 10m54s
Details
CI / status-check (pull_request) Successful in 3s
Details
e9cf6d9658 
Adds ProviderType.GEMINI to the provider registry fallback order, right after
ProviderType.GOOGLE. This ensures Gemini-only users can use auto-discovery via
get_default_provider_type() when only GEMINI_API_KEY is set.

Also removes the @tdd_expected_fail tag from the TDD scenario in features/
tdd_gemini_fallback_order_4750.feature since the test now passes.
HAL9001 requested changes 2026-05-11 23:07:51 +00:00
HAL9001 left a comment
Copy link

Review Summary

The code change itself is correct and minimal — adding ProviderType.GEMINI to FALLBACK_ORDER directly after ProviderType.GOOGLE is exactly what issue #4750 requires, and the TDD regression test is properly updated (the @tdd_expected_fail tag removed correctly since the fix is now applied). All core CI gates pass (lint, typecheck, security, unit_tests, coverage ≥ 97%, integration_tests, e2e_tests).

However, there are 5 process/administrative blockers that must be resolved before this can be approved. These are not about the code logic — the fix is correct — but they are required by CONTRIBUTING.md and cannot be waived.

❌ Blocker 1: Commit missing ISSUES CLOSED: footer

The commit e9cf6d96 has no ISSUES CLOSED: #4750 (or Refs: #4750) footer in its message. Per CONTRIBUTING.md, every commit footer must reference its issue:

fix(providers): add ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER

...(body)...

ISSUES CLOSED: #4750

Please amend the commit (if not yet pushed elsewhere) or add a follow-up fixup commit.

❌ Blocker 2: PR body missing closing keyword

The PR description has no Closes #4750 or Fixes #4750 statement. CONTRIBUTING.md requires:

PRs without issue reference will NOT be reviewed / merged.

Please add Closes #4750 to the PR description body.

❌ Blocker 3: No milestone assigned to PR

Issue #4750 belongs to milestone v3.5.0. The PR must be assigned the same milestone. Currently the PR has no milestone.

Please assign milestone v3.5.0 to this PR.

❌ Blocker 4: No Type/ label applied

This PR fixes a bug — it requires exactly one Type/ label: Type/Bug. Currently the PR has no labels at all.

Please apply the Type/Bug label.

❌ Blocker 5: CHANGELOG.md not updated

No entry was added to CHANGELOG.md under ## [Unreleased] for this fix. Per CONTRIBUTING.md, every commit must include a changelog entry. Expected entry (example):

- **ProviderType.GEMINI missing from ProviderRegistry.FALLBACK_ORDER** (#4750): Added
  `ProviderType.GEMINI` to `ProviderRegistry.FALLBACK_ORDER` after `ProviderType.GOOGLE`,
  ensuring Gemini-only users can use auto-discovery via `get_default_provider_type()` when
  only `GEMINI_API_KEY` is set.

Please add this entry in the same commit (or a fixup commit) to keep changes atomic.

⚠️ Non-blocking: CI benchmark-regression is failing

The CI / benchmark-regression check is failing ("Failing after 1m41s"). All other CI gates pass.

This single-line change is unlikely to cause a performance regression, so this failure is probably pre-existing or transient. However, CI must be fully green before merge. Please investigate whether this failure is caused by this PR or is a pre-existing issue in master, and either fix it or document that it is unrelated.

⚠️ Advisory: Branch naming convention

The branch fix/gemini-fallback-order does not follow the project convention. For a bug fix on milestone v3.5.0 (m5), the expected branch name is bugfix/m5-gemini-fallback-order. Since the PR is already open, renaming the branch is not required — this is advisory only for future PRs.

✅ What is correct

  • The fix is minimal and correct: ProviderType.GEMINI added after ProviderType.GOOGLE in FALLBACK_ORDER — exactly as specified in #4750
  • The @tdd_expected_fail tag is correctly removed from features/tdd_gemini_fallback_order_4750.feature
  • The TDD regression test @tdd_issue_4750 is retained and will now pass
  • Commit message first line follows Conventional Changelog format: fix(providers): add ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER
  • All primary CI gates pass (lint, typecheck, security, unit_tests, coverage, integration_tests, e2e_tests)

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

## Review Summary The code change itself is correct and minimal — adding `ProviderType.GEMINI` to `FALLBACK_ORDER` directly after `ProviderType.GOOGLE` is exactly what issue #4750 requires, and the TDD regression test is properly updated (the `@tdd_expected_fail` tag removed correctly since the fix is now applied). All core CI gates pass (lint, typecheck, security, unit_tests, coverage ≥ 97%, integration_tests, e2e_tests). However, there are **5 process/administrative blockers** that must be resolved before this can be approved. These are not about the code logic — the fix is correct — but they are required by CONTRIBUTING.md and cannot be waived. --- ### ❌ Blocker 1: Commit missing `ISSUES CLOSED:` footer The commit `e9cf6d96` has no `ISSUES CLOSED: #4750` (or `Refs: #4750`) footer in its message. Per CONTRIBUTING.md, every commit footer must reference its issue: ``` fix(providers): add ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER ...(body)... ISSUES CLOSED: #4750 ``` Please amend the commit (if not yet pushed elsewhere) or add a follow-up fixup commit. --- ### ❌ Blocker 2: PR body missing closing keyword The PR description has no `Closes #4750` or `Fixes #4750` statement. CONTRIBUTING.md requires: > PRs without issue reference will NOT be reviewed / merged. Please add `Closes #4750` to the PR description body. --- ### ❌ Blocker 3: No milestone assigned to PR Issue #4750 belongs to milestone **v3.5.0**. The PR must be assigned the same milestone. Currently the PR has no milestone. Please assign milestone **v3.5.0** to this PR. --- ### ❌ Blocker 4: No `Type/` label applied This PR fixes a bug — it requires exactly one `Type/` label: **`Type/Bug`**. Currently the PR has no labels at all. Please apply the `Type/Bug` label. --- ### ❌ Blocker 5: CHANGELOG.md not updated No entry was added to `CHANGELOG.md` under `## [Unreleased]` for this fix. Per CONTRIBUTING.md, every commit must include a changelog entry. Expected entry (example): ```markdown - **ProviderType.GEMINI missing from ProviderRegistry.FALLBACK_ORDER** (#4750): Added `ProviderType.GEMINI` to `ProviderRegistry.FALLBACK_ORDER` after `ProviderType.GOOGLE`, ensuring Gemini-only users can use auto-discovery via `get_default_provider_type()` when only `GEMINI_API_KEY` is set. ``` Please add this entry in the same commit (or a fixup commit) to keep changes atomic. --- ### ⚠️ Non-blocking: CI `benchmark-regression` is failing The `CI / benchmark-regression` check is failing ("Failing after 1m41s"). All other CI gates pass. This single-line change is unlikely to cause a performance regression, so this failure is probably pre-existing or transient. However, CI must be fully green before merge. Please investigate whether this failure is caused by this PR or is a pre-existing issue in master, and either fix it or document that it is unrelated. --- ### ⚠️ Advisory: Branch naming convention The branch `fix/gemini-fallback-order` does not follow the project convention. For a bug fix on milestone v3.5.0 (m5), the expected branch name is `bugfix/m5-gemini-fallback-order`. Since the PR is already open, renaming the branch is not required — this is advisory only for future PRs. --- ### ✅ What is correct - The fix is minimal and correct: `ProviderType.GEMINI` added after `ProviderType.GOOGLE` in `FALLBACK_ORDER` — exactly as specified in #4750 - The `@tdd_expected_fail` tag is correctly removed from `features/tdd_gemini_fallback_order_4750.feature` - The TDD regression test `@tdd_issue_4750` is retained and will now pass - Commit message first line follows Conventional Changelog format: `fix(providers): add ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER` - All primary CI gates pass (lint, typecheck, security, unit_tests, coverage, integration_tests, e2e_tests) --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/tdd_gemini_fallback_order_4750.feature
@ -4,3 +4,3 @@
So that Gemini-only users can use auto-discovery without setting GOOGLE_API_KEY
@tdd_issue @tdd_issue_4750 @tdd_expected_fail
@tdd_issue @tdd_issue_4750
HAL9001 commented 2026-05-11 23:07:51 +00:00
Owner
Copy link

✅ Correct: The @tdd_expected_fail tag has been properly removed now that the fix is applied. The @tdd_issue and @tdd_issue_4750 tags are retained correctly as permanent regression guards. No changes needed here.

✅ Correct: The `@tdd_expected_fail` tag has been properly removed now that the fix is applied. The `@tdd_issue` and `@tdd_issue_4750` tags are retained correctly as permanent regression guards. No changes needed here.
src/cleveragents/providers/registry.py
HAL9001 commented 2026-05-11 23:07:51 +00:00
Owner
Copy link

BLOCKER: CHANGELOG.md not updated

This commit introduces a bug fix but CHANGELOG.md has no corresponding entry under ## [Unreleased]. Per CONTRIBUTING.md, every commit must include a changelog update in the same commit.

Expected entry under ### Fixed or as a top-level bullet:

- **ProviderType.GEMINI missing from ProviderRegistry.FALLBACK_ORDER** (#4750): Added
  `ProviderType.GEMINI` to `ProviderRegistry.FALLBACK_ORDER` after `ProviderType.GOOGLE`,
  ensuring Gemini-only users can use `get_default_provider_type()` successfully when only
  `GEMINI_API_KEY` is set.

Please add this in a fixup commit alongside the ISSUES CLOSED footer fix.

**BLOCKER: CHANGELOG.md not updated** This commit introduces a bug fix but `CHANGELOG.md` has no corresponding entry under `## [Unreleased]`. Per CONTRIBUTING.md, every commit must include a changelog update in the same commit. Expected entry under `### Fixed` or as a top-level bullet: ```markdown - **ProviderType.GEMINI missing from ProviderRegistry.FALLBACK_ORDER** (#4750): Added `ProviderType.GEMINI` to `ProviderRegistry.FALLBACK_ORDER` after `ProviderType.GOOGLE`, ensuring Gemini-only users can use `get_default_provider_type()` successfully when only `GEMINI_API_KEY` is set. ``` Please add this in a fixup commit alongside the ISSUES CLOSED footer fix.
HAL9001 commented 2026-05-11 23:08:01 +00:00
Owner
Copy link

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

--- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9000 commented 2026-06-10 18:05:07 +00:00
Author
Owner
Copy link

[CONTROLLER-CLOSE:Gate 1:full_duplicate]

PR #11110 has an identical title and scope to five other open PRs (#10906, #10986, #10997, #11003, #11064), all attempting to add ProviderType.GEMINI to the fallback order. PR #10906 is the canonical—it has the most substantial changes (27 additions, 8 files) suggesting it is the original attempt. The anchor PR #11110 (2 additions, 1 deletion, 2 files) is a minimal re-attempt with less comprehensive coverage. This is a clear full duplicate.

Decision:

  • Gate: Gate 1
  • Reason category: full_duplicate
  • Canonical (if duplicate): #10906
  • LLM confidence (when applicable): high
  • LLM reasoning (when applicable): PR #11110 has an identical title and scope to five other open PRs (#10906, #10986, #10997, #11003, #11064), all attempting to add ProviderType.GEMINI to the fallback order. PR #10906 is the canonical—it has the most substantial changes (27 additions, 8 files) suggesting it is the original attempt. The anchor PR #11110 (2 additions, 1 deletion, 2 files) is a minimal re-attempt with less comprehensive coverage. This is a clear full duplicate.

Audit ID: 161243

Automated by the CleverAgents controller pipeline.
Identity: HAL9000 (pipeline action)

[CONTROLLER-CLOSE:Gate 1:full_duplicate] PR #11110 has an identical title and scope to five other open PRs (#10906, #10986, #10997, #11003, #11064), all attempting to add ProviderType.GEMINI to the fallback order. PR #10906 is the canonical—it has the most substantial changes (27 additions, 8 files) suggesting it is the original attempt. The anchor PR #11110 (2 additions, 1 deletion, 2 files) is a minimal re-attempt with less comprehensive coverage. This is a clear full duplicate. Decision: - Gate: Gate 1 - Reason category: full_duplicate - Canonical (if duplicate): #10906 - LLM confidence (when applicable): high - LLM reasoning (when applicable): PR #11110 has an identical title and scope to five other open PRs (#10906, #10986, #10997, #11003, #11064), all attempting to add ProviderType.GEMINI to the fallback order. PR #10906 is the canonical—it has the most substantial changes (27 additions, 8 files) suggesting it is the original attempt. The anchor PR #11110 (2 additions, 1 deletion, 2 files) is a minimal re-attempt with less comprehensive coverage. This is a clear full duplicate. Audit ID: 161243 --- Automated by the CleverAgents controller pipeline. Identity: HAL9000 (pipeline action) <!-- controller:fingerprint:005c72372dc81413 -->
HAL9000 closed this pull request 2026-06-10 18:05:08 +00:00
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 52s
Details
CI / helm (pull_request) Successful in 56s
Details
CI / build (pull_request) Successful in 1m13s
Required
Details
CI / benchmark-regression (pull_request) Failing after 1m41s
Details
CI / quality (pull_request) Successful in 1m51s
Required
Details
CI / lint (pull_request) Successful in 1m55s
Required
Details
CI / typecheck (pull_request) Successful in 2m2s
Required
Details
CI / security (pull_request) Successful in 2m1s
Required
Details
CI / integration_tests (pull_request) Successful in 4m0s
Required
Details
CI / e2e_tests (pull_request) Successful in 5m10s
Details
CI / unit_tests (pull_request) Successful in 5m25s
Required
Details
CI / docker (pull_request) Successful in 2m0s
Required
Details
CI / coverage (pull_request) Successful in 10m54s
Required
Details
CI / status-check (pull_request) Successful in 3s
Details

Pull request closed

Please reopen this pull request to perform a merge.
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.

  
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 labels
auto/needs-reevaluation
controller-managed
overdue
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!11110
No description provided.