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

chore(ci): consolidate uv cache key across all workflow jobs #1644

Merged
freemo merged 1 commit from task/ci-consolidate-uv-cache-key into master 2026-04-03 01:07:34 +00:00
Conversation 5 Commits 1 Files changed 2 +32 -16
freemo commented 2026-04-02 23:22:18 +00:00
Owner
Copy link

Summary

Consolidates all per-job uv cache key prefixes across CI workflow files into a single shared key (uv-${{ hashFiles('pyproject.toml') }}), eliminating redundant package downloads and reducing CI wall-clock time. Also adds missing uv cache steps to the build job in ci.yml and to nightly-quality.yml.

Changes

  • Unified cache key in .forgejo/workflows/ci.yml: Replaced six distinct per-job cache key prefixes (uv-lint-, uv-typecheck-, uv-security-, uv-quality-, uv-tests-, uv-coverage-) with the single shared key uv-${{ hashFiles('pyproject.toml') }} across all 8 jobs. This means all jobs now hit the same cache entry when pyproject.toml is unchanged, rather than each job independently downloading and storing its own copy of the dependency set.
  • Updated restore-keys fallback in ci.yml: Changed all per-job restore-key prefixes (e.g., uv-lint-) to the generic uv- prefix, enabling partial cache hits across pyproject.toml changes and ensuring the fallback is consistent with the new unified key scheme.
  • Added missing uv cache step to the build job in ci.yml: The build job previously had no caching at all. It now participates in the shared cache, preventing unnecessary re-downloads during build runs.
  • Added uv caching to .forgejo/workflows/nightly-quality.yml: This workflow had no cache configuration whatsoever. An 8-line cache step using the same uv-${{ hashFiles('pyproject.toml') }} key and uv- restore-key has been added for consistency and to benefit nightly runs from cached dependencies.

Design Decisions

  • pyproject.toml as the cache key hash source: pyproject.toml is the single source of truth for Python dependencies in this project. Hashing it produces a cache key that is stable when dependencies are unchanged and invalidates correctly when they are updated — no other file (e.g., uv.lock) is needed for this purpose.
  • Generic uv- restore-key fallback: Using uv- as the fallback allows any previously cached environment to serve as a warm starting point after a pyproject.toml change, minimising cold-cache penalty during dependency updates.
  • Same pattern applied to nightly-quality.yml: Consistency across all workflow files reduces maintenance burden and ensures nightly runs benefit from the same caching strategy as the main CI pipeline.
  • No Python code changes: This PR is strictly a CI infrastructure change. All modifications are confined to YAML workflow files, making it low-risk and easy to review.

Testing

  • Unit tests (Behave): N/A — no Python source changes
  • Integration tests (Robot): N/A — no Python source changes
  • Coverage: N/A — no Python source changes
  • Benchmarks: Not needed

Note on visible CI failures: The lint, typecheck, security, and unit_tests failures visible in this PR's CI run are pre-existing issues on master that are unrelated to this change. This PR modifies only YAML workflow files; no Python code was altered.

Modules Affected

  • .forgejo/workflows/ci.yml — 16 lines changed (cache key consolidation across 8 jobs + added missing build job cache step)
  • .forgejo/workflows/nightly-quality.yml — 8 lines added (new uv cache step)

Related Issues

Closes #1535

Checklist

  • All nox stages pass (lint, typecheck, unit_tests, integration_tests, coverage_report)
  • Coverage >= 97%
  • No # type: ignore directives
  • Commit message follows Conventional Changelog format
  • Implementation aligns with docs/specification.md

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-worker

## Summary Consolidates all per-job `uv` cache key prefixes across CI workflow files into a single shared key (`uv-${{ hashFiles('pyproject.toml') }}`), eliminating redundant package downloads and reducing CI wall-clock time. Also adds missing `uv` cache steps to the `build` job in `ci.yml` and to `nightly-quality.yml`. ## Changes - **Unified cache key in `.forgejo/workflows/ci.yml`**: Replaced six distinct per-job cache key prefixes (`uv-lint-`, `uv-typecheck-`, `uv-security-`, `uv-quality-`, `uv-tests-`, `uv-coverage-`) with the single shared key `uv-${{ hashFiles('pyproject.toml') }}` across all 8 jobs. This means all jobs now hit the same cache entry when `pyproject.toml` is unchanged, rather than each job independently downloading and storing its own copy of the dependency set. - **Updated `restore-keys` fallback in `ci.yml`**: Changed all per-job restore-key prefixes (e.g., `uv-lint-`) to the generic `uv-` prefix, enabling partial cache hits across `pyproject.toml` changes and ensuring the fallback is consistent with the new unified key scheme. - **Added missing `uv` cache step to the `build` job in `ci.yml`**: The `build` job previously had no caching at all. It now participates in the shared cache, preventing unnecessary re-downloads during build runs. - **Added `uv` caching to `.forgejo/workflows/nightly-quality.yml`**: This workflow had no cache configuration whatsoever. An 8-line cache step using the same `uv-${{ hashFiles('pyproject.toml') }}` key and `uv-` restore-key has been added for consistency and to benefit nightly runs from cached dependencies. ## Design Decisions - **`pyproject.toml` as the cache key hash source**: `pyproject.toml` is the single source of truth for Python dependencies in this project. Hashing it produces a cache key that is stable when dependencies are unchanged and invalidates correctly when they are updated — no other file (e.g., `uv.lock`) is needed for this purpose. - **Generic `uv-` restore-key fallback**: Using `uv-` as the fallback allows any previously cached environment to serve as a warm starting point after a `pyproject.toml` change, minimising cold-cache penalty during dependency updates. - **Same pattern applied to `nightly-quality.yml`**: Consistency across all workflow files reduces maintenance burden and ensures nightly runs benefit from the same caching strategy as the main CI pipeline. - **No Python code changes**: This PR is strictly a CI infrastructure change. All modifications are confined to YAML workflow files, making it low-risk and easy to review. ## Testing - Unit tests (Behave): N/A — no Python source changes - Integration tests (Robot): N/A — no Python source changes - Coverage: N/A — no Python source changes - Benchmarks: Not needed > **Note on visible CI failures**: The lint, typecheck, security, and unit_tests failures visible in this PR's CI run are pre-existing issues on `master` that are unrelated to this change. This PR modifies only YAML workflow files; no Python code was altered. ## Modules Affected - `.forgejo/workflows/ci.yml` — 16 lines changed (cache key consolidation across 8 jobs + added missing `build` job cache step) - `.forgejo/workflows/nightly-quality.yml` — 8 lines added (new `uv` cache step) ## Related Issues Closes #1535 ## Checklist - [ ] All nox stages pass (lint, typecheck, unit_tests, integration_tests, coverage_report) - [ ] Coverage >= 97% - [ ] No `# type: ignore` directives - [ ] Commit message follows Conventional Changelog format - [ ] Implementation aligns with docs/specification.md --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
chore(ci): consolidate uv cache key across all workflow jobs
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Failing after 24s
Details
CI / helm (pull_request) Successful in 32s
Details
CI / typecheck (pull_request) Failing after 50s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Has been skipped
Details
CI / security (pull_request) Failing after 53s
Details
CI / unit_tests (pull_request) Failing after 1m51s
Details
CI / docker (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 3m19s
Details
CI / quality (pull_request) Successful in 3m43s
Details
CI / e2e_tests (pull_request) Failing after 15m3s
Details
CI / integration_tests (pull_request) Failing after 20m57s
Details
CI / status-check (pull_request) Failing after 1s
Details
99aa459bad 
Replace per-job cache key prefixes (uv-lint-, uv-typecheck-, uv-security-,
uv-quality-, uv-tests-, uv-coverage-) with a single shared key
uv-${{ hashFiles('pyproject.toml') }} across all jobs in ci.yml.

Also add a missing uv cache step to the build job and add uv caching
to nightly-quality.yml, which previously had no cache at all.

All jobs now share the same cache entry when pyproject.toml is unchanged,
eliminating redundant package downloads and reducing CI wall-clock time.

ISSUES CLOSED: #1535
freemo commented 2026-04-02 23:22:51 +00:00
Author
Owner
Copy link

Review claimed by reviewer pool instance pr-reviewer-pool-3983434-1775170710. Dispatching independent code review.

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

Review claimed by reviewer pool instance pr-reviewer-pool-3983434-1775170710. Dispatching independent code review. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
freemo added this to the v3.8.0 milestone 2026-04-02 23:22:51 +00:00
freemo commented 2026-04-02 23:39:41 +00:00
Author
Owner
Copy link

Label compliance fix applied:

  • Added missing labels: Priority/Medium, State/In Review, Type/Task
  • Reason: PR was missing all required labels. This is a CI chore task (chore(ci): consolidate uv cache key), so Type/Task and Priority/Medium are appropriate. State set to State/In Review as this is an open PR.

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

Label compliance fix applied: - Added missing labels: `Priority/Medium`, `State/In Review`, `Type/Task` - Reason: PR was missing all required labels. This is a CI chore task (`chore(ci): consolidate uv cache key`), so `Type/Task` and `Priority/Medium` are appropriate. State set to `State/In Review` as this is an open PR. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
freemo commented 2026-04-03 01:07:21 +00:00
Author
Owner
Copy link

Independent Code Review — APPROVED ✅

Summary

This PR consolidates the uv cache key across all CI workflow jobs, replacing 6 distinct per-job cache key prefixes with a single shared key uv-${{ hashFiles('pyproject.toml') }}. It also adds missing cache steps to the build job and nightly-quality.yml.

Review Findings

✅ Specification Alignment

  • CI infrastructure change only — no Python code modified, no spec impact.
  • Aligns with the project's CI/CD practices.

✅ Correctness

  • Cache key consolidation is sound: All jobs install from the same pyproject.toml, so sharing a single uv download cache is correct. The ~/.cache/uv directory stores downloaded packages (not virtual environments), making cross-job sharing safe.
  • Restore-key fallback uv-: Correctly provides warm cache hits across pyproject.toml changes.
  • Build job cache addition: Previously had no caching at all — this is a clear improvement, correctly placed after pip install uv and before nox -s build.
  • Nightly quality cache addition: Same correct pattern, properly placed in the workflow step sequence.

✅ PR Metadata Compliance

  • Title follows Conventional Changelog format: chore(ci): consolidate uv cache key across all workflow jobs
  • Closes #1535 (closing keyword present)
  • Milestone: v3.8.0 (matches linked issue)
  • Labels: Type/Task, Priority/Medium, State/In Review — all required labels present
  • Single atomic commit

✅ CI Status

  • CI failures (lint, typecheck, security, unit_tests, integration_tests, e2e_tests) are pre-existing on master — confirmed by checking master's head commit (921c13f) which shows identical failures.
  • This PR modifies only YAML workflow files; it cannot introduce or fix Python-level CI failures.

✅ Security

  • No secrets, credentials, or sensitive data in the changes.
  • Cache paths and keys are standard CI patterns.

Verdict

Clean, well-documented CI infrastructure improvement. The approach is correct, the implementation is consistent across all jobs, and the PR goes beyond the issue scope by also adding caching to previously uncached jobs. No concerns. Proceeding to merge.

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

## Independent Code Review — APPROVED ✅ ### Summary This PR consolidates the `uv` cache key across all CI workflow jobs, replacing 6 distinct per-job cache key prefixes with a single shared key `uv-${{ hashFiles('pyproject.toml') }}`. It also adds missing cache steps to the `build` job and `nightly-quality.yml`. ### Review Findings #### ✅ Specification Alignment - CI infrastructure change only — no Python code modified, no spec impact. - Aligns with the project's CI/CD practices. #### ✅ Correctness - **Cache key consolidation is sound**: All jobs install from the same `pyproject.toml`, so sharing a single `uv` download cache is correct. The `~/.cache/uv` directory stores downloaded packages (not virtual environments), making cross-job sharing safe. - **Restore-key fallback `uv-`**: Correctly provides warm cache hits across `pyproject.toml` changes. - **Build job cache addition**: Previously had no caching at all — this is a clear improvement, correctly placed after `pip install uv` and before `nox -s build`. - **Nightly quality cache addition**: Same correct pattern, properly placed in the workflow step sequence. #### ✅ PR Metadata Compliance - Title follows Conventional Changelog format: `chore(ci): consolidate uv cache key across all workflow jobs` - Closes #1535 (closing keyword present) - Milestone: v3.8.0 (matches linked issue) - Labels: `Type/Task`, `Priority/Medium`, `State/In Review` — all required labels present - Single atomic commit #### ✅ CI Status - CI failures (lint, typecheck, security, unit_tests, integration_tests, e2e_tests) are **pre-existing on master** — confirmed by checking master's head commit (`921c13f`) which shows identical failures. - This PR modifies only YAML workflow files; it cannot introduce or fix Python-level CI failures. #### ✅ Security - No secrets, credentials, or sensitive data in the changes. - Cache paths and keys are standard CI patterns. ### Verdict Clean, well-documented CI infrastructure improvement. The approach is correct, the implementation is consistent across all jobs, and the PR goes beyond the issue scope by also adding caching to previously uncached jobs. No concerns. Proceeding to merge. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
freemo merged commit fe1c3f7cc8 into master 2026-04-03 01:07:34 +00:00
freemo deleted branch task/ci-consolidate-uv-cache-key 2026-04-03 01:07:34 +00:00
freemo reviewed 2026-04-03 01:09:10 +00:00
freemo left a comment
Copy link

Review: PR #1644 — chore(ci): consolidate uv cache key across all workflow jobs

Decision: APPROVED ✅ — Proceeding to merge

Clean YAML-only change consolidating 6 per-job cache keys into single shared key. Adds missing cache to build job and nightly-quality workflow. pyproject.toml hash is the correct cache key source. Low risk.

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

## Review: PR #1644 — chore(ci): consolidate uv cache key across all workflow jobs **Decision: APPROVED ✅ — Proceeding to merge** Clean YAML-only change consolidating 6 per-job cache keys into single shared key. Adds missing cache to build job and nightly-quality workflow. `pyproject.toml` hash is the correct cache key source. Low risk. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
freemo commented 2026-04-03 01:11:11 +00:00
Author
Owner
Copy link

Code Review: ✅ APPROVED

Reviewed against: CONTRIBUTING.md rules, CI best practices.

Summary:

Consolidates all per-job uv cache key prefixes into a single shared key. Adds missing cache steps to build job and nightly-quality.yml.

  • ✅ pyproject.toml is the correct hash source for dependency caching
  • ✅ Generic uv- restore-key fallback enables partial cache hits
  • ✅ Consistent pattern across all workflow files
  • ✅ Missing build job cache eliminates unnecessary re-downloads

Proceeding to merge.

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

## Code Review: ✅ APPROVED **Reviewed against:** CONTRIBUTING.md rules, CI best practices. ### Summary: Consolidates all per-job `uv` cache key prefixes into a single shared key. Adds missing cache steps to `build` job and `nightly-quality.yml`. - ✅ `pyproject.toml` is the correct hash source for dependency caching - ✅ Generic `uv-` restore-key fallback enables partial cache hits - ✅ Consistent pattern across all workflow files - ✅ Missing `build` job cache eliminates unnecessary re-downloads **Proceeding to merge.** --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
Sign in to join this conversation.
Reviewers
No reviewers
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
v3.8.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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.

Dependencies

No dependencies set.

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