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

Build: Added back the benchmark tests but made them so they only run after pull requests into master #9004

Closed
freemo wants to merge 1 commit from benchmark-ci into master
pull from: benchmark-ci
merge into: cleveragents:master
Conversation 7 Commits 1 Files changed 1 +126
freemo commented 2026-04-14 05:01:36 +00:00
Owner
Copy link
No description provided.
Build: Added back the benchmark tests but made them so they only run after pull requests into master
All checks were successful
CI / lint (pull_request) Successful in 27s
Details
CI / build (pull_request) Successful in 27s
Details
CI / helm (pull_request) Successful in 25s
Details
CI / typecheck (pull_request) Successful in 54s
Details
CI / quality (pull_request) Successful in 56s
Details
CI / security (pull_request) Successful in 1m1s
Details
CI / push-validation (pull_request) Successful in 39s
Details
CI / e2e_tests (pull_request) Successful in 4m15s
Details
CI / integration_tests (pull_request) Successful in 4m19s
Details
CI / unit_tests (pull_request) Successful in 5m24s
Details
CI / docker (pull_request) Successful in 1m17s
Details
CI / coverage (pull_request) Successful in 10m49s
Details
CI / status-check (pull_request) Successful in 1s
Details
d5ab9fc53e
freemo scheduled this pull request to auto merge when all checks succeed 2026-04-14 05:02:32 +00:00
HAL9000 added this to the v3.2.0 milestone 2026-04-14 05:23:38 +00:00
HAL9000 commented 2026-04-14 05:23:59 +00:00
Owner
Copy link

Thank you for this contribution, @freemo.

This PR has been received and logged. Based on the title, the bot understands this change to involve the following:

  • Benchmark tests have been re-added to the CI pipeline after a prior removal.
  • The benchmark tests are now gated so they only execute when a pull request targets the master branch, preventing unnecessary benchmark runs on feature or development branch PRs.

This is a CI/build infrastructure improvement that reduces noise in the pipeline while preserving benchmark coverage at the point of integration.

Action requested: The PR body is currently empty. Please consider adding a brief description to help reviewers understand the scope of the change, which workflow files were modified, and any relevant context (e.g., why the benchmarks were previously removed, what triggered the re-addition). This will expedite the review process.

Triage applied:

  • Labels: Type/Testing, Priority/Medium, State/In Review, MoSCoW/Should have
  • Milestone: v3.2.0 (current active milestone)

The automated review pipeline will assess this PR in due course.

Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: human-liaison-pool-supervisor
Worker: [AUTO-HUMAN-1]

Thank you for this contribution, @freemo. This PR has been received and logged. Based on the title, the bot understands this change to involve the following: - Benchmark tests have been re-added to the CI pipeline after a prior removal. - The benchmark tests are now gated so they only execute when a pull request targets the `master` branch, preventing unnecessary benchmark runs on feature or development branch PRs. This is a CI/build infrastructure improvement that reduces noise in the pipeline while preserving benchmark coverage at the point of integration. **Action requested:** The PR body is currently empty. Please consider adding a brief description to help reviewers understand the scope of the change, which workflow files were modified, and any relevant context (e.g., why the benchmarks were previously removed, what triggered the re-addition). This will expedite the review process. **Triage applied:** - Labels: `Type/Testing`, `Priority/Medium`, `State/In Review`, `MoSCoW/Should have` - Milestone: `v3.2.0` (current active milestone) The automated review pipeline will assess this PR in due course. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: human-liaison-pool-supervisor Worker: [AUTO-HUMAN-1]
HAL9000 commented 2026-04-14 05:25:34 +00:00
Owner
Copy link

Summary:

  • Discovered that the PR is missing a description and a linked issue reference required by CONTRIBUTING.

Actions Taken:

  • Applied State/In Review, Priority/Medium, Type/Testing, and MoSCoW/Should have labels to categorize the PR.

Requests:

  • Please update the PR description with a clear summary of the changes and how benchmarks are exercised.
  • Please link the corresponding issue (e.g., reference it in the description) so we can trace the work item.

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor

Summary: - Discovered that the PR is missing a description and a linked issue reference required by CONTRIBUTING. Actions Taken: - Applied State/In Review, Priority/Medium, Type/Testing, and MoSCoW/Should have labels to categorize the PR. Requests: - Please update the PR description with a clear summary of the changes and how benchmarks are exercised. - Please link the corresponding issue (e.g., reference it in the description) so we can trace the work item. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor ---
HAL9000 commented 2026-04-14 05:25:38 +00:00
Owner
Copy link

[GROOMED]

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor

[GROOMED] --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor ---
HAL9001 requested changes 2026-04-15 00:22:35 +00:00
HAL9001 left a comment
Copy link

Code Review: REQUEST CHANGES

Thank you for this CI infrastructure improvement, @freemo. The benchmark workflow addition is a good idea, but this PR has several blocking issues that must be resolved before it can be merged.

✅ Passing Criteria

Check Status
CI / lint ✅ Passed
CI / typecheck ✅ Passed
CI / security ✅ Passed
CI / quality ✅ Passed
CI / unit_tests ✅ Passed
CI / integration_tests ✅ Passed
CI / e2e_tests ✅ Passed
CI / build ✅ Passed
CI / helm ✅ Passed
CI / docker ✅ Passed
CI / coverage ✅ Passed
CI / push-validation ✅ Passed
CI / status-check ✅ Passed
Milestone assigned (v3.2.0) ✅ Present
Exactly one Type/ label (Type/Testing) ✅ Present

❌ Blocking Issues

1. Missing ISSUES CLOSED: #N commit footer

The commit message is:

Build: Added back the benchmark tests but made them so they only run after pull requests into master

It is missing the required ISSUES CLOSED: #N footer as mandated by CONTRIBUTING.md. Please amend the commit to include the footer referencing the relevant issue number.

2. PR body is empty — no linked issue / closing keyword

The PR description is completely empty. CONTRIBUTING.md requires:

  • A description of the change
  • A closing keyword (e.g., Closes #NNNN) linking to the relevant issue

Please update the PR body with a description and a Closes #NNNN reference.

3. CHANGELOG.md not updated

Only .forgejo/workflows/master.yml was changed. CHANGELOG.md must be updated to document this CI infrastructure change.

4. CONTRIBUTORS.md not updated

CONTRIBUTORS.md must be updated as required by CONTRIBUTING.md.

⚠️ Workflow Logic Bugs

The new workflow file has two significant logic errors:

Bug 1 — Dead job condition: The benchmark-regression job has:

if: forgejo.event_name == 'pull_request'

However, the workflow trigger is:

on:
    push:
        branches: [master, develop]

This workflow only fires on push events, so forgejo.event_name will always be push — the benchmark-regression job will never execute. To run on pull requests, the trigger must include pull_request: as an event.

Bug 2 — Missing job dependencies: The benchmark-regression job declares:

needs: [lint, typecheck, security, quality]

But none of those jobs (lint, typecheck, security, quality) are defined in this workflow file. This would cause the workflow to fail immediately if it ever ran.

Please fix both bugs — either add a pull_request: trigger and define the prerequisite jobs, or remove the needs: block and adjust the trigger accordingly.

Summary

Requirement Status
All CI checks pass ✅
Coverage >= 97% ✅ (CI coverage job passed)
Commit has ISSUES CLOSED: #N footer ❌ Missing
PR closes a linked issue ❌ Missing
Milestone assigned ✅
Exactly one Type/ label ✅
CHANGELOG.md updated ❌ Missing
CONTRIBUTORS.md updated ❌ Missing
Workflow logic correct ❌ Two bugs found

4 blocking process violations + 2 workflow logic bugs must be resolved before this PR can be approved.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-9004]

## Code Review: REQUEST CHANGES Thank you for this CI infrastructure improvement, @freemo. The benchmark workflow addition is a good idea, but this PR has several blocking issues that must be resolved before it can be merged. --- ### ✅ Passing Criteria | Check | Status | |---|---| | CI / lint | ✅ Passed | | CI / typecheck | ✅ Passed | | CI / security | ✅ Passed | | CI / quality | ✅ Passed | | CI / unit_tests | ✅ Passed | | CI / integration_tests | ✅ Passed | | CI / e2e_tests | ✅ Passed | | CI / build | ✅ Passed | | CI / helm | ✅ Passed | | CI / docker | ✅ Passed | | CI / coverage | ✅ Passed | | CI / push-validation | ✅ Passed | | CI / status-check | ✅ Passed | | Milestone assigned (v3.2.0) | ✅ Present | | Exactly one Type/ label (Type/Testing) | ✅ Present | --- ### ❌ Blocking Issues #### 1. Missing `ISSUES CLOSED: #N` commit footer The commit message is: ``` Build: Added back the benchmark tests but made them so they only run after pull requests into master ``` It is missing the required `ISSUES CLOSED: #N` footer as mandated by CONTRIBUTING.md. Please amend the commit to include the footer referencing the relevant issue number. #### 2. PR body is empty — no linked issue / closing keyword The PR description is completely empty. CONTRIBUTING.md requires: - A description of the change - A closing keyword (e.g., `Closes #NNNN`) linking to the relevant issue Please update the PR body with a description and a `Closes #NNNN` reference. #### 3. CHANGELOG.md not updated Only `.forgejo/workflows/master.yml` was changed. CHANGELOG.md must be updated to document this CI infrastructure change. #### 4. CONTRIBUTORS.md not updated CONTRIBUTORS.md must be updated as required by CONTRIBUTING.md. --- ### ⚠️ Workflow Logic Bugs The new workflow file has two significant logic errors: **Bug 1 — Dead job condition:** The `benchmark-regression` job has: ```yaml if: forgejo.event_name == 'pull_request' ``` However, the workflow trigger is: ```yaml on: push: branches: [master, develop] ``` This workflow only fires on `push` events, so `forgejo.event_name` will always be `push` — the `benchmark-regression` job will **never execute**. To run on pull requests, the trigger must include `pull_request:` as an event. **Bug 2 — Missing job dependencies:** The `benchmark-regression` job declares: ```yaml needs: [lint, typecheck, security, quality] ``` But none of those jobs (`lint`, `typecheck`, `security`, `quality`) are defined in this workflow file. This would cause the workflow to fail immediately if it ever ran. Please fix both bugs — either add a `pull_request:` trigger and define the prerequisite jobs, or remove the `needs:` block and adjust the trigger accordingly. --- ### Summary | Requirement | Status | |---|---| | All CI checks pass | ✅ | | Coverage >= 97% | ✅ (CI coverage job passed) | | Commit has `ISSUES CLOSED: #N` footer | ❌ Missing | | PR closes a linked issue | ❌ Missing | | Milestone assigned | ✅ | | Exactly one Type/ label | ✅ | | CHANGELOG.md updated | ❌ Missing | | CONTRIBUTORS.md updated | ❌ Missing | | Workflow logic correct | ❌ Two bugs found | **4 blocking process violations + 2 workflow logic bugs must be resolved before this PR can be approved.** --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9004]
HAL9001 commented 2026-04-15 00:23:12 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES

This PR has been formally reviewed and changes are required before it can be merged.

Blocking Issues (4)

  1. Missing ISSUES CLOSED: #N commit footer — The commit message lacks the required footer referencing the closed issue number.
  2. Empty PR body / no linked issue — The PR description is empty; a Closes #NNNN closing keyword is required.
  3. CHANGELOG.md not updated — This file must be updated to document the CI infrastructure change.
  4. CONTRIBUTORS.md not updated — This file must be updated per CONTRIBUTING.md requirements.

Workflow Logic Bugs (2)

  • Bug 1: benchmark-regression job has if: forgejo.event_name == 'pull_request' but the workflow only triggers on push events — the job will never run.
  • Bug 2: benchmark-regression job declares needs: [lint, typecheck, security, quality] but those jobs are not defined in this workflow file.

Passing Criteria

  • ✅ All 13 CI checks passed
  • ✅ Milestone v3.2.0 assigned
  • ✅ Exactly one Type/ label (Type/Testing)

Please address all 4 blocking process violations and 2 workflow bugs, then request a re-review.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-9004]

**Code Review Decision: REQUEST CHANGES** This PR has been formally reviewed and changes are required before it can be merged. ### Blocking Issues (4) 1. **Missing `ISSUES CLOSED: #N` commit footer** — The commit message lacks the required footer referencing the closed issue number. 2. **Empty PR body / no linked issue** — The PR description is empty; a `Closes #NNNN` closing keyword is required. 3. **CHANGELOG.md not updated** — This file must be updated to document the CI infrastructure change. 4. **CONTRIBUTORS.md not updated** — This file must be updated per CONTRIBUTING.md requirements. ### Workflow Logic Bugs (2) - **Bug 1:** `benchmark-regression` job has `if: forgejo.event_name == 'pull_request'` but the workflow only triggers on `push` events — the job will never run. - **Bug 2:** `benchmark-regression` job declares `needs: [lint, typecheck, security, quality]` but those jobs are not defined in this workflow file. ### Passing Criteria - ✅ All 13 CI checks passed - ✅ Milestone v3.2.0 assigned - ✅ Exactly one Type/ label (Type/Testing) Please address all 4 blocking process violations and 2 workflow bugs, then request a re-review. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9004]
HAL9000 commented 2026-04-15 03:16:35 +00:00
Owner
Copy link

@freemo — The automated review pool has completed a code review of PR #9004 and has submitted REQUEST CHANGES. The following issues must be addressed before this PR can be merged:

Blocking Process Issues (4)

  1. Missing ISSUES CLOSED: #N commit footer — The commit message must include a footer referencing the closed issue number (e.g., ISSUES CLOSED: #NNNN).
  2. Empty PR body / no linked issue — The PR description is currently empty. A Closes #NNNN closing keyword referencing the linked issue is required per CONTRIBUTING.md.
  3. CHANGELOG.md not updated — This CI infrastructure change must be documented in CHANGELOG.md.
  4. CONTRIBUTORS.md not updated — This file must be updated per CONTRIBUTING.md requirements.

Workflow Logic Bugs (2)

  1. benchmark-regression job condition mismatch — The job has if: forgejo.event_name == 'pull_request' but the workflow only triggers on push events. The job will never run as currently configured.
  2. Missing job dependencies — The benchmark-regression job declares needs: [lint, typecheck, security, quality] but those jobs are not defined in this workflow file.

What Passes

All 13 CI checks pass, milestone v3.2.0 is assigned, and the Type/Testing label is correctly set.

Please address the 4 process violations and 2 workflow bugs, then push an updated commit. The review pool will re-review once changes are pushed.

Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: human-liaison-pool-supervisor
Worker: [AUTO-HUMAN-7]

@freemo — The automated review pool has completed a code review of PR #9004 and has submitted REQUEST CHANGES. The following issues must be addressed before this PR can be merged: ### Blocking Process Issues (4) 1. **Missing `ISSUES CLOSED: #N` commit footer** — The commit message must include a footer referencing the closed issue number (e.g., `ISSUES CLOSED: #NNNN`). 2. **Empty PR body / no linked issue** — The PR description is currently empty. A `Closes #NNNN` closing keyword referencing the linked issue is required per CONTRIBUTING.md. 3. **CHANGELOG.md not updated** — This CI infrastructure change must be documented in CHANGELOG.md. 4. **CONTRIBUTORS.md not updated** — This file must be updated per CONTRIBUTING.md requirements. ### Workflow Logic Bugs (2) 1. **`benchmark-regression` job condition mismatch** — The job has `if: forgejo.event_name == 'pull_request'` but the workflow only triggers on `push` events. The job will never run as currently configured. 2. **Missing job dependencies** — The `benchmark-regression` job declares `needs: [lint, typecheck, security, quality]` but those jobs are not defined in this workflow file. ### What Passes All 13 CI checks pass, milestone v3.2.0 is assigned, and the `Type/Testing` label is correctly set. Please address the 4 process violations and 2 workflow bugs, then push an updated commit. The review pool will re-review once changes are pushed. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: human-liaison-pool-supervisor Worker: [AUTO-HUMAN-7]
freemo force-pushed benchmark-ci from d5ab9fc53e
All checks were successful
CI / lint (pull_request) Successful in 27s
Details
CI / build (pull_request) Successful in 27s
Details
CI / helm (pull_request) Successful in 25s
Details
CI / typecheck (pull_request) Successful in 54s
Details
CI / quality (pull_request) Successful in 56s
Details
CI / security (pull_request) Successful in 1m1s
Details
CI / push-validation (pull_request) Successful in 39s
Details
CI / e2e_tests (pull_request) Successful in 4m15s
Details
CI / integration_tests (pull_request) Successful in 4m19s
Details
CI / unit_tests (pull_request) Successful in 5m24s
Details
CI / docker (pull_request) Successful in 1m17s
Details
CI / coverage (pull_request) Successful in 10m49s
Details
CI / status-check (pull_request) Successful in 1s
Details
to 201de8bbf3
All checks were successful
CI / push-validation (pull_request) Successful in 21s
Details
CI / helm (pull_request) Successful in 23s
Details
CI / lint (pull_request) Successful in 39s
Details
CI / quality (pull_request) Successful in 40s
Details
CI / typecheck (pull_request) Successful in 55s
Details
CI / security (pull_request) Successful in 56s
Details
CI / build (pull_request) Successful in 3m20s
Details
CI / integration_tests (pull_request) Successful in 4m3s
Details
CI / e2e_tests (pull_request) Successful in 7m38s
Details
CI / unit_tests (pull_request) Successful in 8m46s
Details
CI / docker (pull_request) Successful in 8s
Details
CI / coverage (pull_request) Successful in 13m22s
Details
CI / status-check (pull_request) Successful in 2s
Details
2026-04-15 17:09:14 +00:00 Compare
freemo commented 2026-04-15 17:10:01 +00:00
Author
Owner
Copy link

merged in directly

merged in directly
freemo closed this pull request 2026-04-15 17:10:01 +00:00
All checks were successful
CI / push-validation (pull_request) Successful in 21s
Details
CI / helm (pull_request) Successful in 23s
Details
CI / lint (pull_request) Successful in 39s
Required
Details
CI / quality (pull_request) Successful in 40s
Required
Details
CI / typecheck (pull_request) Successful in 55s
Required
Details
CI / security (pull_request) Successful in 56s
Required
Details
CI / build (pull_request) Successful in 3m20s
Required
Details
CI / integration_tests (pull_request) Successful in 4m3s
Required
Details
CI / e2e_tests (pull_request) Successful in 7m38s
Details
CI / unit_tests (pull_request) Successful in 8m46s
Required
Details
CI / docker (pull_request) Successful in 8s
Required
Details
CI / coverage (pull_request) Successful in 13m22s
Required
Details
CI / status-check (pull_request) Successful in 2s
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.

  
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.2.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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!9004
No description provided.