test(e2e): workflow example 18 — container with remote repo clone (trusted profile) #820

Merged

hurui200320 merged 1 commit from test/e2e-wf18-container-clone into master 2026-03-30 11:40:57 +00:00

Conversation 5 Commits 1 Files changed 5 +370

freemo commented 2026-03-13 17:16:57 +00:00

Owner

Copy link

Summary

E2E test for Specification Workflow Example 18: Container with Remote Repo Clone using the trusted automation profile. Tests the full container-instance workflow including --clone-into, plan-level execution environment with fallback priority, and the complete plan lifecycle.

Closes #764

ISSUES CLOSED: #764

Changes

E2E Test (robot/e2e/wf18_container_clone.robot)

• Container-instance resource with --clone-into: Registers a container-instance resource with the --clone-into REPO_URL:CONTAINER_PATH flag per the spec (not git-checkout).
• Two-step project creation: Uses project create then project link-resource to match the spec's demonstrated flow for Example 18.
• Dynamic actor selection: Detects ANTHROPIC_API_KEY vs OPENAI_API_KEY and selects the appropriate actor (following m6_acceptance.robot pattern).
• Plan use with execution environment: Passes --execution-environment container and --execution-env-priority fallback with --automation-profile trusted. Note: the spec shows --execution-environment cloud/build-env (a resource name), but the current CLI only supports enum values (host or container); resource-name-based resolution is future work.
• Full plan lifecycle: Strategize → Execute → Diff → Apply → Status.
• lifecycle-apply --yes: Uses --yes flag to skip the confirmation prompt in non-interactive (CI) execution, consistent with all other E2E tests.
• Soft assertions for AC-4/5/6: Container/clone evidence (AC-4), execution environment resolution evidence (AC-5), and apply commit/push evidence (AC-6) use Run Keyword And Warn On Failure to handle LLM output non-determinism.
• Negative assertions: Traceback and INTERNAL error checks on every step.
• Positive assertion on link-resource: Verifies the resource name appears in the output.
• Pre/post commit count: Captures commit count before and after apply; asserts count does not decrease (flexible — LLM may or may not generate file changes).
• Post-lifecycle fixture verification: Verifies fixture files (deploy_manager.py, Dockerfile) still exist after the full lifecycle.
• ULID regex: Uses Crockford base32 character set [0-9A-HJKMNP-TV-Z]{26}.
• Unique suffix: UUID-based suffix on resource/project/action names for parallel CI safety (all names include ${RUN_SUFFIX}).
• Force Tags E2E: Suite-level tag instead of per-test [Tags].
• [Timeout] 20 minutes: Comfortable margin over cumulative step timeouts.
• [Teardown]: Per-test teardown that logs completion.
• Two-call pattern comment: Explains the sequential plan execute calls (Strategize then Execute).
• Dockerfile fixture comment: Clarifies that the Dockerfile is fixture data only, never built by the test.
• Skip If No LLM Keys: Graceful skip when no LLM API keys are available.
• --format plain: All CLI commands use --format plain for consistency.

CLI Enhancement (src/cleveragents/cli/commands/resource.py)

• New --clone-into flag on resource add command. Accepts REPO_URL:CONTAINER_PATH format, stores the value as a clone_into property on the resource.
• Type restriction: --clone-into is only accepted for container-instance and devcontainer-instance resource types. Using it with other types emits a validation error.
• Format validation: Validates that the --clone-into value contains a : separator with non-empty segments on both sides. Uses rsplit(":", 1) to handle URLs with ports.

Behave Tests (features/resource_cli_coverage.feature)

• 4 new scenarios for --clone-into CLI coverage:
  1. resource add container-instance with --clone-into stores clone_into property successfully.
  2. --clone-into on non-container type (git-checkout) fails with validation error.
  3. --clone-into with invalid format (no colon separator) fails with validation error.
  4. --clone-into with missing path segment fails with validation error.

CHANGELOG (CHANGELOG.md)

• Updated entry to clearly indicate --clone-into is a new CLI flag introduced in this PR, with input validation and type restriction.

Rebase and Fix Notes

• Rebased onto latest master (commit 5ddc04bc), resolving merge conflicts in CHANGELOG.md and src/cleveragents/cli/commands/resource.py. Both the new --mount flag (from WF17/PR merged to master) and --clone-into flag (from this PR) are preserved.
• Fixed broken E2E test: Added missing --yes flag to plan lifecycle-apply command call. The --yes flag was introduced to skip the confirmation prompt in non-interactive mode; all other E2E tests already use it. Without --yes, the command failed with rc=1 when run in CI (no terminal available for prompting).

Manual Verification

Prerequisites

• ANTHROPIC_API_KEY or OPENAI_API_KEY environment variable set

Commands

nox -e e2e_tests   # runs all E2E tests including WF18

What to Look For

• WF18 test passes (or skips gracefully if no LLM keys)
• All other E2E tests still pass
• nox -e lint, nox -e typecheck, nox -e unit_tests, nox -e integration_tests, nox -e coverage_report all pass

## Summary E2E test for Specification Workflow Example 18: Container with Remote Repo Clone using the `trusted` automation profile. Tests the full container-instance workflow including `--clone-into`, plan-level execution environment with `fallback` priority, and the complete plan lifecycle. Closes #764 ISSUES CLOSED: #764 ## Changes ### E2E Test (`robot/e2e/wf18_container_clone.robot`) - **Container-instance resource with `--clone-into`:** Registers a `container-instance` resource with the `--clone-into REPO_URL:CONTAINER_PATH` flag per the spec (not `git-checkout`). - **Two-step project creation:** Uses `project create` then `project link-resource` to match the spec's demonstrated flow for Example 18. - **Dynamic actor selection:** Detects `ANTHROPIC_API_KEY` vs `OPENAI_API_KEY` and selects the appropriate actor (following `m6_acceptance.robot` pattern). - **Plan use with execution environment:** Passes `--execution-environment container` and `--execution-env-priority fallback` with `--automation-profile trusted`. Note: the spec shows `--execution-environment cloud/build-env` (a resource name), but the current CLI only supports enum values (`host` or `container`); resource-name-based resolution is future work. - **Full plan lifecycle:** Strategize → Execute → Diff → Apply → Status. - **`lifecycle-apply --yes`:** Uses `--yes` flag to skip the confirmation prompt in non-interactive (CI) execution, consistent with all other E2E tests. - **Soft assertions for AC-4/5/6:** Container/clone evidence (AC-4), execution environment resolution evidence (AC-5), and apply commit/push evidence (AC-6) use `Run Keyword And Warn On Failure` to handle LLM output non-determinism. - **Negative assertions:** `Traceback` and `INTERNAL` error checks on every step. - **Positive assertion on link-resource:** Verifies the resource name appears in the output. - **Pre/post commit count:** Captures commit count before and after apply; asserts count does not decrease (flexible — LLM may or may not generate file changes). - **Post-lifecycle fixture verification:** Verifies fixture files (`deploy_manager.py`, `Dockerfile`) still exist after the full lifecycle. - **ULID regex:** Uses Crockford base32 character set `[0-9A-HJKMNP-TV-Z]{26}`. - **Unique suffix:** UUID-based suffix on resource/project/action names for parallel CI safety (all names include `${RUN_SUFFIX}`). - **`Force Tags E2E`:** Suite-level tag instead of per-test `[Tags]`. - **`[Timeout] 20 minutes`:** Comfortable margin over cumulative step timeouts. - **`[Teardown]`:** Per-test teardown that logs completion. - **Two-call pattern comment:** Explains the sequential `plan execute` calls (Strategize then Execute). - **Dockerfile fixture comment:** Clarifies that the Dockerfile is fixture data only, never built by the test. - **`Skip If No LLM Keys`:** Graceful skip when no LLM API keys are available. - **`--format plain`:** All CLI commands use `--format plain` for consistency. ### CLI Enhancement (`src/cleveragents/cli/commands/resource.py`) - **New `--clone-into` flag** on `resource add` command. Accepts `REPO_URL:CONTAINER_PATH` format, stores the value as a `clone_into` property on the resource. - **Type restriction:** `--clone-into` is only accepted for `container-instance` and `devcontainer-instance` resource types. Using it with other types emits a validation error. - **Format validation:** Validates that the `--clone-into` value contains a `:` separator with non-empty segments on both sides. Uses `rsplit(":", 1)` to handle URLs with ports. ### Behave Tests (`features/resource_cli_coverage.feature`) - **4 new scenarios** for `--clone-into` CLI coverage: 1. `resource add container-instance` with `--clone-into` stores `clone_into` property successfully. 2. `--clone-into` on non-container type (`git-checkout`) fails with validation error. 3. `--clone-into` with invalid format (no colon separator) fails with validation error. 4. `--clone-into` with missing path segment fails with validation error. ### CHANGELOG (`CHANGELOG.md`) - Updated entry to clearly indicate `--clone-into` is a new CLI flag introduced in this PR, with input validation and type restriction. ## Rebase and Fix Notes - **Rebased onto latest `master`** (commit `5ddc04bc`), resolving merge conflicts in `CHANGELOG.md` and `src/cleveragents/cli/commands/resource.py`. Both the new `--mount` flag (from WF17/PR merged to master) and `--clone-into` flag (from this PR) are preserved. - **Fixed broken E2E test:** Added missing `--yes` flag to `plan lifecycle-apply` command call. The `--yes` flag was introduced to skip the confirmation prompt in non-interactive mode; all other E2E tests already use it. Without `--yes`, the command failed with rc=1 when run in CI (no terminal available for prompting). ## Manual Verification ### Prerequisites - `ANTHROPIC_API_KEY` or `OPENAI_API_KEY` environment variable set ### Commands ```bash nox -e e2e_tests # runs all E2E tests including WF18 ``` ### What to Look For - WF18 test passes (or skips gracefully if no LLM keys) - All other E2E tests still pass - `nox -e lint`, `nox -e typecheck`, `nox -e unit_tests`, `nox -e integration_tests`, `nox -e coverage_report` all pass

freemo added this to the v3.8.0 milestone 2026-03-13 17:17:06 +00:00

freemo added the

State

In Review

Type

Testing

labels 2026-03-13 17:17:06 +00:00

freemo force-pushed test/e2e-wf18-container-clone from 5505f1669d to 4e307bc57d 2026-03-13 17:28:57 +00:00 Compare

freemo force-pushed test/e2e-wf18-container-clone from 4e307bc57d to 602cfbfd2d 2026-03-13 17:47:00 +00:00 Compare

freemo force-pushed test/e2e-wf18-container-clone from 602cfbfd2d to d840408f49 2026-03-13 18:13:20 +00:00 Compare

freemo force-pushed test/e2e-wf18-container-clone from d840408f49 to 0eccc8f397 2026-03-13 18:25:25 +00:00 Compare

freemo referenced this pull request 2026-03-13 19:21:28 +00:00

test(e2e): workflow example 18 — container with remote repo clone (trusted profile) #764

freemo force-pushed test/e2e-wf18-container-clone from 0eccc8f397 to 70d9d17532 2026-03-13 23:19:54 +00:00 Compare

freemo added the

Priority

Medium

label 2026-03-14 04:10:25 +00:00

freemo commented 2026-03-14 04:45:27 +00:00

Author

Owner

Copy link

PM Review — Day 34

Status: Mergeable, 0 reviews, M9 (v3.8.0)
Author: @freemo

E2E test for WF18 (container with remote repo clone, trusted profile). M9 — lowest urgency.

Action Items

Who	Action	Deadline
Peer review deferred to M9 sprint

## PM Review — Day 34 **Status**: Mergeable, 0 reviews, M9 (v3.8.0) **Author**: @freemo E2E test for WF18 (container with remote repo clone, trusted profile). M9 — lowest urgency. ### Action Items | Who | Action | Deadline | |-----|--------|----------| | Peer review deferred to M9 sprint | | |

freemo added a new dependency 2026-03-16 02:42:20 +00:00

#627 Implement @tdd_expected_fail tag handling in Behave environment

freemo added a new dependency 2026-03-16 02:42:21 +00:00

#628 Implement @tdd_expected_fail tag handling in Robot Framework

freemo added a new dependency 2026-03-16 02:42:21 +00:00

#965 refactor(testing): rename tdd_bug/tdd_bug_N tags to tdd_issue/tdd_issue_N across Behave and Robot Framework

freemo commented 2026-03-16 09:35:14 +00:00

Author

Owner

Copy link

PM Status — Day 36 (2026-03-16)

Day 34 review assignment deadline check. This PR has 0 reviewer activity after 2 days.

Priority note: M3 PRs take precedence. Reviewers should complete M3 reviews first, then address M4+ PRs in milestone order.

Assigned reviewer: Please acknowledge and provide an ETA for your review, or flag if reassignment is needed.

## PM Status — Day 36 (2026-03-16) Day 34 review assignment deadline check. This PR has 0 reviewer activity after 2 days. **Priority note**: M3 PRs take precedence. Reviewers should complete M3 reviews first, then address M4+ PRs in milestone order. **Assigned reviewer**: Please acknowledge and provide an ETA for your review, or flag if reassignment is needed.

hurui200320 was assigned by freemo 2026-03-16 22:24:15 +00:00

freemo commented 2026-03-16 22:24:21 +00:00

Author

Owner

Copy link

@hurui200320 I am going to have you take over this PR, it is mostly completed but is waiting on #628 and #966 One is yours and one is Brent's. Please be sure to get this PR and the two blocking PRs I listed in asap, thanks.

@hurui200320 I am going to have you take over this PR, it is mostly completed but is waiting on https://git.cleverthis.com/cleveragents/cleveragents-core/issues/628 and https://git.cleverthis.com/cleveragents/cleveragents-core/issues/966 One is yours and one is Brent's. Please be sure to get this PR and the two blocking PRs I listed in asap, thanks.

freemo commented 2026-03-17 18:34:10 +00:00

Author

Owner

Copy link

PM Status — Day 37

Reviewers assigned. This PR needs at least 2 approving reviews per CONTRIBUTING.md before merge.

Author: Please ensure this PR is rebased on latest master and all quality gates pass before requesting merge.

---

PM status — Day 37

## PM Status — Day 37 Reviewers assigned. This PR needs at least 2 approving reviews per `CONTRIBUTING.md` before merge. **Author**: Please ensure this PR is rebased on latest `master` and all quality gates pass before requesting merge. --- *PM status — Day 37*

freemo requested review from hamza.khyari 2026-03-17 18:34:19 +00:00

hurui200320 force-pushed test/e2e-wf18-container-clone from 70d9d17532 to 310ae288f7 2026-03-18 08:35:48 +00:00 Compare

freemo commented 2026-03-19 04:58:03 +00:00

Author

Owner

Copy link

Code Review — PR #820

(Cannot submit formal approval — self-authored PR.)

E2E test for WF18. Well-structured with proper labels, milestone, and issue linkage. No issues found.

## Code Review — PR #820 *(Cannot submit formal approval — self-authored PR.)* E2E test for WF18. Well-structured with proper labels, milestone, and issue linkage. No issues found.

freemo requested reviews from brent.edwards, CoreRasurae 2026-03-19 05:20:03 +00:00

hurui200320 force-pushed test/e2e-wf18-container-clone from 310ae288f7 to 5e83950533 2026-03-20 07:59:39 +00:00 Compare

hurui200320 force-pushed test/e2e-wf18-container-clone from 5e83950533 to c658b928c3 2026-03-20 08:40:26 +00:00 Compare

hurui200320 force-pushed test/e2e-wf18-container-clone from c658b928c3 to 4f12abdf20 2026-03-20 09:38:44 +00:00 Compare

hurui200320 force-pushed test/e2e-wf18-container-clone from 4f12abdf20 to 13a51b1494 2026-03-23 04:10:55 +00:00 Compare

hurui200320 force-pushed test/e2e-wf18-container-clone from 13a51b1494 to be37ef3dcb 2026-03-24 05:40:21 +00:00 Compare

freemo removed a dependency 2026-03-26 15:14:38 +00:00

#965 refactor(testing): rename tdd_bug/tdd_bug_N tags to tdd_issue/tdd_issue_N across Behave and Robot Framework

freemo added a new dependency 2026-03-26 15:14:41 +00:00

#965 refactor(testing): rename tdd_bug/tdd_bug_N tags to tdd_issue/tdd_issue_N across Behave and Robot Framework

freemo removed a dependency 2026-03-26 18:28:26 +00:00

#965 refactor(testing): rename tdd_bug/tdd_bug_N tags to tdd_issue/tdd_issue_N across Behave and Robot Framework

hurui200320 force-pushed test/e2e-wf18-container-clone from be37ef3dcb to 92cb31306d 2026-03-27 10:00:15 +00:00 Compare

hurui200320 force-pushed test/e2e-wf18-container-clone from 92cb31306d to 7f5c376a64 2026-03-30 09:54:54 +00:00 Compare

hurui200320 force-pushed test/e2e-wf18-container-clone from 7f5c376a64 to 3b47eccb43 2026-03-30 10:31:17 +00:00 Compare

hurui200320 force-pushed test/e2e-wf18-container-clone from 3b47eccb43 to 1613d6f4ad 2026-03-30 10:33:09 +00:00 Compare

hurui200320 force-pushed test/e2e-wf18-container-clone from 1613d6f4ad to 9cace15d6e 2026-03-30 11:17:52 +00:00 Compare

hurui200320 scheduled this pull request to auto merge when all checks succeed 2026-03-30 11:18:15 +00:00

hurui200320 merged commit 9cace15d6e into master 2026-03-30 11:40:57 +00:00

hurui200320 deleted branch test/e2e-wf18-container-clone 2026-03-30 11:40:57 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

hamza.khyari

brent.edwards

CoreRasurae

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

hurui200320

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on

#627 Implement @tdd_expected_fail tag handling in Behave environment

cleveragents/cleveragents-core

#628 Implement @tdd_expected_fail tag handling in Robot Framework

cleveragents/cleveragents-core

Reference

cleveragents/cleveragents-core!820

No description provided.