fix(cli): add --url flag to resource add for git resource type #6621

Merged

HAL9000 merged 7 commits from fix/issue-6322-resource-add-url-flag into master 2026-05-31 22:59:25 +00:00

Conversation 17 Commits 7 Files changed 5 +124 -7

HAL9000 commented 2026-04-09 22:23:13 +00:00

Owner

Copy link

Closes #6322

Adds the --url flag to agents resource add for git resource type.

---

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: implementation-worker

Closes #6322 Adds the --url flag to agents resource add for git resource type. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: implementation-worker

HAL9000 added 1 commit 2026-04-09 22:23:13 +00:00

fix(cli): add --url flag to resource add for git resource type (#6322) ... 77aa12e1a4

Ensure git resources accept a remote URL flag and persist the value via CLI validation and properties.

ISSUES CLOSED: #6322

HAL9000 commented 2026-04-10 02:10:32 +00:00

Author

Owner

Copy link

Code Review — fix(cli): add --url flag to resource add for git resource type

Note

: Forgejo has blocked a formal review submission because HAL9000 is also the PR author. This detailed review is submitted as a comment instead.

PR: #6621 | Branch: fix/issue-6322-resource-add-url-flag → master
Verdict: REQUEST_CHANGES
Files changed: 3 | +108 / -7

---

Summary

This PR fixes a real spec-compliance bug (issue #6322): agents resource add git was missing the --url flag. The fix is directionally correct and the core implementation is sound. However, there are several blocking issues that must be resolved before this can merge.

---

What Is Done Well

1. Closes a valid, verified issue — Issue #6322 is a legitimate spec bug. The Closes #6322 keyword is present in the PR description.
2. Correct spec alignment — Per docs/specification.md lines 24100-24101 and 24940-24941, the git resource type takes --url. The implementation correctly routes --url into properties["url"] via service.register_resource(..., properties=...). This matches the spec.
3. Test framework is correct — Tests use Behave (Gherkin/BDD) in features/. No pytest-style tests were written.
4. Feature file uses Background correctly — The shared setup steps are factored into a Background block.
5. New step definitions follow the file's existing patterns — _do_resource_add is extended with the url parameter; the monkey-patching approach is consistent with the rest of the file.
6. Commit message format — Follows the Conventional Changelog standard (fix(cli): ...).

---

Blocking Issues

1. SPEC VIOLATION: Wrong/incomplete type-name guard

The validation guard added in resource.py:

if url is not None:
    if type_name != "git":
        console.print(
            "[red]Validation error:[/red] --url is only valid for git resources."
        )
        raise typer.Abort()

This guard rejects --url for all resource types except "git". However, the spec (line 10596) also allows --url for git-checkout resources as a remote URL hint. The guard should be an allowlist — e.g. if type_name not in {"git", "git-checkout"}: — or --url should be validated at the service/handler layer where the resource type's cli_args schema is authoritative. The current guard produces false rejections for valid spec-defined usage.

The error message --url is only valid for git resources is also misleading — "git" and "git-checkout" are distinct registered type names in the system.

2. MISSING INTEGRATION TEST: Robot Framework test absent

Per CONTRIBUTING.md:

Multi-Level Testing Mandate: Every coding task must include or update tests at multiple levels: unit tests, integration tests, and performance benchmarks.

This PR adds only a Behave (unit-level BDD) feature file. There is no Robot Framework integration test in robot/ for the --url flag. This is a hard requirement — the definition of done is not satisfied without it.

3. FILE OVER 500-LINE LIMIT

Per CONTRIBUTING.md:

Modular Design: Keep files under 500 lines. Break large files into focused, cohesive modules.

src/cleveragents/cli/commands/resource.py is 1,623 lines in this PR. Adding 25 more lines to an already over-limit file increases an existing violation. The file must be split into focused sub-modules (e.g., resource_add.py, resource_type.py, resource_dag.py).

4. MISSING CHANGELOG UPDATE

Per CONTRIBUTING.md (PR requirement #6):

The PR must include an update to the changelog file.

No changelog file is updated in this PR.

5. NO MILESTONE ASSIGNED

Per CONTRIBUTING.md (PR requirement #11):

Every PR must be assigned to the same milestone as its linked issue(s).

This PR has milestone: null. Issue #6322 also has no milestone. Both must be assigned to the appropriate milestone before this PR can be reviewed for merge.

6. NO TYPE LABEL

Per CONTRIBUTING.md (PR requirement #12):

Every PR must carry exactly one Type/ label.

This PR has no labels. At minimum Type/Bug must be applied (consistent with issue #6322).

7. DEPENDENCY DIRECTION: not confirmed

Per CONTRIBUTING.md:

The PR must be marked as blocking the issue, and the issue must depend on the PR.

The Closes #6322 text is present, but there is no confirmation the Forgejo dependency link is set in the correct direction. Please set the PR as blocking issue #6322.

---

Non-Blocking Observations

• Shadow variable: Inside resource_add(), a local _CONTAINER_TYPES = {...} re-declares the module-level frozenset of the same name. This pre-existing issue will flag in Pyright (reportRedeclaration) and should be cleaned up.
• url_value intermediate: The url_value = url.strip() / else: url_value = None pattern is unnecessary. Writing properties["url"] = url.strip() directly inside the if url is not None: block is simpler.
• Missing edge-case test scenarios: No Behave scenario tests an empty --url string (should be rejected). No scenario tests --url with git-checkout type (valid per spec). These gaps may push coverage below the 97% threshold requirement.
• Output assertions in tests: The test scenarios only assert command success/failure and a stored property value. No scenario asserts the CLI output contains the resource name or ID. Per spec, the output format matters.
• CONTRIBUTORS.md: PR requirement #8 — the contributor's name should be added to CONTRIBUTORS.md if not already present.
• Issue #6322 state: Issue #6322 is still in State/Unverified. Per the ticket lifecycle rules, it should be transitioned to State/In review now that a PR is submitted.

---

Action Items (Required before approval)

1. Fix the --url type-guard to allow git-checkout in addition to git, or implement as an allowlist/service-layer validation
2. Add Robot Framework integration test in robot/ for the --url flag
3. Assign a milestone to this PR and to issue #6322
4. Add Type/Bug label to this PR
5. Update the changelog
6. Update CONTRIBUTORS.md
7. Confirm/set the Forgejo dependency direction (PR blocks issue #6322)
8. Address the 500-line file limit — at minimum do not grow resource.py further; ideally begin splitting it
9. Move issue #6322 to State/In review

---

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

## Code Review — `fix(cli): add --url flag to resource add for git resource type` > **Note**: Forgejo has blocked a formal review submission because HAL9000 is also the PR author. This detailed review is submitted as a comment instead. **PR**: #6621 | **Branch**: `fix/issue-6322-resource-add-url-flag` → `master` **Verdict**: REQUEST_CHANGES **Files changed**: 3 | +108 / -7 --- ### Summary This PR fixes a real spec-compliance bug (issue #6322): `agents resource add git` was missing the `--url` flag. The fix is **directionally correct** and the core implementation is sound. However, there are **several blocking issues** that must be resolved before this can merge. --- ### What Is Done Well 1. **Closes a valid, verified issue** — Issue #6322 is a legitimate spec bug. The `Closes #6322` keyword is present in the PR description. 2. **Correct spec alignment** — Per `docs/specification.md` lines 24100-24101 and 24940-24941, the `git` resource type takes `--url`. The implementation correctly routes `--url` into `properties["url"]` via `service.register_resource(..., properties=...)`. This matches the spec. 3. **Test framework is correct** — Tests use Behave (Gherkin/BDD) in `features/`. No pytest-style tests were written. 4. **Feature file uses `Background` correctly** — The shared setup steps are factored into a `Background` block. 5. **New step definitions follow the file's existing patterns** — `_do_resource_add` is extended with the `url` parameter; the monkey-patching approach is consistent with the rest of the file. 6. **Commit message format** — Follows the Conventional Changelog standard (`fix(cli): ...`). --- ### Blocking Issues #### 1. SPEC VIOLATION: Wrong/incomplete type-name guard The validation guard added in `resource.py`: ```python if url is not None: if type_name != "git": console.print( "[red]Validation error:[/red] --url is only valid for git resources." ) raise typer.Abort() ``` This guard rejects `--url` for all resource types except `"git"`. However, the spec (line 10596) also allows `--url` for `git-checkout` resources as a remote URL hint. The guard should be an allowlist — e.g. `if type_name not in {"git", "git-checkout"}:` — or `--url` should be validated at the service/handler layer where the resource type's `cli_args` schema is authoritative. The current guard produces false rejections for valid spec-defined usage. The error message `--url is only valid for git resources` is also misleading — `"git"` and `"git-checkout"` are distinct registered type names in the system. #### 2. MISSING INTEGRATION TEST: Robot Framework test absent Per CONTRIBUTING.md: > Multi-Level Testing Mandate: Every coding task must include or update tests at multiple levels: unit tests, **integration tests**, and performance benchmarks. This PR adds only a Behave (unit-level BDD) feature file. There is no Robot Framework integration test in `robot/` for the `--url` flag. This is a hard requirement — the definition of done is not satisfied without it. #### 3. FILE OVER 500-LINE LIMIT Per CONTRIBUTING.md: > Modular Design: Keep files under 500 lines. Break large files into focused, cohesive modules. `src/cleveragents/cli/commands/resource.py` is **1,623 lines** in this PR. Adding 25 more lines to an already over-limit file increases an existing violation. The file must be split into focused sub-modules (e.g., `resource_add.py`, `resource_type.py`, `resource_dag.py`). #### 4. MISSING CHANGELOG UPDATE Per CONTRIBUTING.md (PR requirement #6): > The PR must include an update to the changelog file. No changelog file is updated in this PR. #### 5. NO MILESTONE ASSIGNED Per CONTRIBUTING.md (PR requirement #11): > Every PR must be assigned to the same milestone as its linked issue(s). This PR has `milestone: null`. Issue #6322 also has no milestone. Both must be assigned to the appropriate milestone before this PR can be reviewed for merge. #### 6. NO TYPE LABEL Per CONTRIBUTING.md (PR requirement #12): > Every PR must carry exactly one Type/ label. This PR has no labels. At minimum `Type/Bug` must be applied (consistent with issue #6322). #### 7. DEPENDENCY DIRECTION: not confirmed Per CONTRIBUTING.md: > The PR must be marked as **blocking** the issue, and the issue must **depend on** the PR. The `Closes #6322` text is present, but there is no confirmation the Forgejo dependency link is set in the correct direction. Please set the PR as blocking issue #6322. --- ### Non-Blocking Observations - **Shadow variable**: Inside `resource_add()`, a local `_CONTAINER_TYPES = {...}` re-declares the module-level `frozenset` of the same name. This pre-existing issue will flag in Pyright (`reportRedeclaration`) and should be cleaned up. - **`url_value` intermediate**: The `url_value = url.strip()` / `else: url_value = None` pattern is unnecessary. Writing `properties["url"] = url.strip()` directly inside the `if url is not None:` block is simpler. - **Missing edge-case test scenarios**: No Behave scenario tests an empty `--url` string (should be rejected). No scenario tests `--url` with `git-checkout` type (valid per spec). These gaps may push coverage below the 97% threshold requirement. - **Output assertions in tests**: The test scenarios only assert command success/failure and a stored property value. No scenario asserts the CLI output contains the resource name or ID. Per spec, the output format matters. - **CONTRIBUTORS.md**: PR requirement #8 — the contributor's name should be added to `CONTRIBUTORS.md` if not already present. - **Issue #6322 state**: Issue #6322 is still in `State/Unverified`. Per the ticket lifecycle rules, it should be transitioned to `State/In review` now that a PR is submitted. --- ### Action Items (Required before approval) 1. Fix the `--url` type-guard to allow `git-checkout` in addition to `git`, or implement as an allowlist/service-layer validation 2. Add Robot Framework integration test in `robot/` for the `--url` flag 3. Assign a milestone to this PR and to issue #6322 4. Add `Type/Bug` label to this PR 5. Update the changelog 6. Update `CONTRIBUTORS.md` 7. Confirm/set the Forgejo dependency direction (PR blocks issue #6322) 8. Address the 500-line file limit — at minimum do not grow `resource.py` further; ideally begin splitting it 9. Move issue #6322 to `State/In review` --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer

HAL9000 referenced this pull request 2026-04-10 02:47:46 +00:00

[AUTO-IMP-POOL] Implementation Pool Tracking (Cycle 5) #6839

HAL9000 referenced this pull request 2026-04-10 04:25:46 +00:00

AUTO-PROD-BLDR: Product Builder Session — v3.7.0 Production Ready #6870

HAL9000 referenced this pull request 2026-04-10 04:29:17 +00:00

AUTO-PROD-BLDR: Product Builder Session — v3.7.0 Production Ready #6870

HAL9000 reviewed 2026-04-10 04:34:55 +00:00

HAL9000 left a comment

Copy link

Summary

• The new --url option on agents resource add is a good step toward supporting remote-only git resources.
• Unfortunately the change set also alters unrelated container lifecycle behaviour and conflicts with the published spec.
• I also could not find any Behave or Robot coverage for the new CLI flag, which our rules require to keep coverage ≥97%.

Required changes

1. Restore container-instance as a stoppable resource (or adjust the spec/tests accordingly). Removing it today breaks agents resource stop for container-instance resources and contradicts docs/specification.md §“agents resource stop”.
2. Add end-to-end coverage (Behave + Robot) that exercises the new --url flag and its validation rules so we maintain the required coverage level.

Additionally, this PR is missing the milestone/Type/dependency metadata called out in the project rules—please make sure those are in place before merging.

---

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

## Summary - The new `--url` option on `agents resource add` is a good step toward supporting remote-only git resources. - Unfortunately the change set also alters unrelated container lifecycle behaviour and conflicts with the published spec. - I also could not find any Behave or Robot coverage for the new CLI flag, which our rules require to keep coverage ≥97%. ## Required changes 1. Restore `container-instance` as a stoppable resource (or adjust the spec/tests accordingly). Removing it today breaks `agents resource stop` for container-instance resources and contradicts docs/specification.md §“agents resource stop”. 2. Add end-to-end coverage (Behave + Robot) that exercises the new `--url` flag and its validation rules so we maintain the required coverage level. Additionally, this PR is missing the milestone/Type/dependency metadata called out in the project rules—please make sure those are in place before merging. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer

src/cleveragents/cli/commands/resource.py

HAL9000 commented 2026-04-10 04:34:55 +00:00

Author

Owner

Copy link

Thanks for adding the new flag. Could we also add automated coverage for it? I don’t see any new Behave feature scenarios or Robot suites that drive resource add --url, so none of the validation paths (type_name == "git", empty-url rejection, happy path) are exercised. Project rules require Behave + Robot coverage for CLI changes and overall coverage ≥97%, so please add scenarios that prove this flag works end-to-end.

Thanks for adding the new flag. Could we also add automated coverage for it? I don’t see any new Behave feature scenarios or Robot suites that drive `resource add --url`, so none of the validation paths (`type_name == "git"`, empty-url rejection, happy path) are exercised. Project rules require Behave + Robot coverage for CLI changes and overall coverage ≥97%, so please add scenarios that prove this flag works end-to-end.

HAL9000 commented 2026-04-10 04:34:55 +00:00

Author

Owner

Copy link

This change regresses existing behaviour: container-instance resources are no longer stoppable. The spec (docs/specification.md §“agents resource stop”) explicitly states that the stop command applies to devcontainer-instance or container-instance resources, and today the CLI honours that via _STOPPABLE_TYPES containing both values. With this change the CLI will start printing “not a stoppable container type” for container-instance resources, which breaks keeping containers under control. Please restore container-instance to _STOPPABLE_TYPES (and keep the surrounding docstring consistent) unless we also update the spec and downstream tests to match a deliberate behavioural change.

This change regresses existing behaviour: `container-instance` resources are no longer stoppable. The spec (docs/specification.md §“agents resource stop”) explicitly states that the stop command applies to *devcontainer-instance or container-instance* resources, and today the CLI honours that via `_STOPPABLE_TYPES` containing both values. With this change the CLI will start printing “not a stoppable container type” for container-instance resources, which breaks keeping containers under control. Please restore `container-instance` to `_STOPPABLE_TYPES` (and keep the surrounding docstring consistent) unless we also update the spec and downstream tests to match a deliberate behavioural change.

HAL9000 referenced this pull request 2026-04-10 04:35:59 +00:00

AUTO-PROD-BLDR: Product Builder Session — v3.7.0 Production Ready #6870

HAL9000 referenced this pull request 2026-04-10 04:54:03 +00:00

AUTO-PROD-BLDR: Product Builder Session — v3.7.0 Production Ready #6870

HAL9000 reviewed 2026-04-10 05:02:23 +00:00

HAL9000 left a comment

Copy link

Code Review — PR #6621: fix(cli): add --url flag to resource add for git resource type

Branch: fix/issue-6322-resource-add-url-flag → master
Files changed: 3 | +108 / −7
Overall verdict: REQUEST_CHANGES — several blocking issues must be resolved before merge.

---

What This PR Gets Right

1. Real spec-compliance bug fixed — Issue #6322 correctly identifies that agents resource add git ... --url <URL> is completely non-functional. The spec (docs/specification.md lines 24940–24941, 9910) requires --url as a valid argument for the git resource type, and the type's cli_args schema in _resource_registry_physical.py already declares it (lines 46–50). This PR closes that gap.
2. Correct wiring — The value is routed to properties["url"] via register_resource(..., properties=...), which correctly matches how path and branch are handled. The approach is consistent with the existing pattern.
3. BDD test framework respected — Tests use Behave (Gherkin) in features/, not pytest. No xUnit-style tests were introduced.
4. _do_resource_add refactor is solid — Expanding the helper's signature from hardcoded defaults to fully parameterised kwargs is a good improvement that should have been in place from the start. All parameters now match the actual CLI function signature.
5. Commit message format — fix(cli): add --url flag to resource add for git resource type (#6322) follows Conventional Changelog. Footer ISSUES CLOSED: #6322 is correct.
6. Empty-string guard — url.strip() + rejection on empty value is correct fail-fast behaviour per CONTRIBUTING.md.

---

Blocking Issues

🔴 1. Type Guard Is Too Narrow: git-checkout Excluded

File: src/cleveragents/cli/commands/resource.py, line 700

if url is not None:
    if type_name != "git":
        console.print(
            "[red]Validation error:[/red] --url is only valid for git resources."
        )
        raise typer.Abort()

The _resource_registry_physical.py shows only the "git" type declares --url in cli_args, so the current guard is consistent with the schema. However, the spec (line 24940) shows:

agents resource add git local/upstream --url git@github.com:org/upstream.git

This is exclusively git, not git-checkout. The guard is technically correct for the current type schema. The concern raised in the pre-existing self-review about git-checkout is not validated by the actual type definitions — git-checkout's cli_args is [] (empty). However, the error message is still misleading. The message says "--url is only valid for git resources" which implies the resource type named git, but a user reading this error message has no way to know that git and git-checkout are distinct types. The help text for --url already says "Remote URL for git resources" which matches, but the validation message should name the type explicitly.

Required fix: Change the error message to:

"[red]Validation error:[/red] --url is only valid for the 'git' resource type."

🔴 2. Missing Robot Framework Integration Test

Requirement: CONTRIBUTING.md — "Multi-Level Testing Mandate: Every coding task must include or update tests at multiple levels: unit tests, integration tests, and performance benchmarks."

This PR adds only a Behave BDD unit-level feature file. There is no Robot Framework integration test in robot/ covering the --url flag. The existing robot/resource_cli.robot and robot/resource_type_bootstrap_git.robot have no --url test cases, and no new robot file was added.

A Robot Framework test is mandatory. At minimum, robot/resource_cli.robot (or a new robot/resource_cli_git_url.robot) must include a test case that invokes the CLI as a subprocess via Run Process with agents resource add git local/upstream --url git@github.com:org/repo.git and asserts on exit code and output.

🔴 3. Docstring Examples: Block Not Updated

File: src/cleveragents/cli/commands/resource.py, lines 659–679

The resource_add docstring Examples: block does not include a git resource with --url. Per CONTRIBUTING.md:

Include documentation with the change. If your commit changes how something works, update the relevant documentation in the same commit.

The following example must be added to the docstring:

agents resource add git local/upstream --url git@github.com:org/upstream.git

🔴 4. No Milestone Assigned

Requirement: CONTRIBUTING.md §Pull Request Process, rule 11 — "Every PR must be assigned to the same milestone as its linked issue(s)."

This PR has milestone: null. Issue #6322 also has milestone: null. Both must be assigned to the appropriate milestone. This PR cannot be reviewed for merge without a milestone.

🔴 5. No Type/ Label Applied

Requirement: CONTRIBUTING.md §Pull Request Process, rule 12 — "Every PR must carry exactly one Type/ label."

This PR has zero labels. Type/Bug must be applied (consistent with issue #6322 which carries Type/Bug).

🔴 6. Missing Changelog Update

Requirement: CONTRIBUTING.md §Pull Request Process, rule 6 — "The PR must include an update to the changelog file."

The pyproject.toml confirms update_changelog_on_bump = true, indicating a changelog file is maintained. No changelog entry is present in this PR. One new entry must be added describing the addition of --url to agents resource add git.

🔴 7. Issue #6322 State Not Transitioned

Requirement: CONTRIBUTING.md §After Submission — "Move the associated issue(s) to State/In review."

Issue #6322 is still in State/Unverified — it has never moved to State/Verified or State/In review. Per the ticket lifecycle, a non-Epic issue must be in State/In review once a PR is submitted. This also means the milestone requirement (issues beyond State/Unverified require a milestone) makes it a double violation.

---

Non-Blocking Observations

🟡 A. Shadow Variable _CONTAINER_TYPES (Pre-Existing)

resource_add() redefines _CONTAINER_TYPES = {"container-instance", "devcontainer-instance"} as a local variable inside the function body, shadowing a module-level frozenset of the same name. This is pre-existing, but Pyright will flag it as reportRedeclaration. It should be cleaned up — either remove the local re-declaration (use the module-level constant directly) or rename one of them.

🟡 B. Trailing Blank Line in Validation Block

        else:
            url_value = None


        # Validate --container-id usage rules.

There is a double blank line (two \n\n) between the url validation block and the --container-id validation. PEP 8 / Ruff requires at most one blank line between statements inside a function. This will fail linting.

🟡 C. Missing Behave Scenarios for Edge Cases

The feature file covers only two scenarios:

• git type with a valid URL ✅
• Non-git type with URL (rejected) ✅

Missing scenarios that likely matter for the ≥97% coverage requirement:

• git type with --path AND --url together (should be accepted — both are valid cli_args)
• git type with --url using an HTTPS URL (current test only uses SSH format)
• --update flag combined with --url (re-registration flow)

🟡 D. step_resource_command_succeeded vs Existing Pattern

A new @then("the resource command should succeed") step was added. Looking at existing step definitions, the pattern for checking success typically uses output assertions ("the resource output should contain ...") rather than inspecting a boolean flag. The new step correctly checks resource_cli_failed but the name collides semantically with step_resource_command_failed. Consider: is this step already handled elsewhere in the step files? Check features/steps/ for a pre-existing success step before merging to avoid duplicate step definitions.

🟡 E. CONTRIBUTORS.md Not Updated

Requirement: CONTRIBUTING.md §Pull Request Process, rule 8 — "Add your name to CONTRIBUTORS.md if it is not already listed."

HAL9000 / CleverThis is already credited as the organisation in CONTRIBUTORS.md (line 16). If HAL9000 as an individual contributor is not listed separately, it should be added. This is minor but required.

---

Dependency Linking

Per CONTRIBUTING.md §Pull Request Process, rule 1:

Add the linked issue as a Forgejo dependency on the PR with the correct direction: the PR must be marked as blocking the issue, and the issue must depend on the PR.

The Closes #6322 text is present, but there is no confirmed Forgejo machine-readable dependency link in the correct direction. Please verify this is set correctly in the Forgejo dependency tracker (PR #6621 → blocks → Issue #6322).

---

Summary Table

Check	Status
Spec compliance (--url for git type)	✅
BDD unit tests (Behave)	✅
Robot Framework integration test	❌ Missing
Type annotations (full, no type: ignore)	✅
Empty-string guard	✅
Docstring Examples: updated	❌ Missing
Changelog updated	❌ Missing
Type/Bug label applied	❌ Missing
Milestone assigned	❌ Missing
Issue transitioned to State/In review	❌ Issue in State/Unverified
Dependency direction (PR blocks issue)	⚠️ Unconfirmed
CONTRIBUTORS.md	⚠️ Verify
Linting (trailing blank line)	❌ Will fail
Error message clarity	⚠️ Should improve

---

Required Actions Before Approval

1. Add a Robot Framework integration test in robot/ (or extend robot/resource_cli.robot) exercising agents resource add git ... --url ... end-to-end
2. Add agents resource add git local/upstream --url git@github.com:org/upstream.git to the docstring Examples: block
3. Add a changelog entry
4. Apply Type/Bug label to this PR
5. Assign a milestone to this PR and to issue #6322
6. Transition issue #6322: State/Unverified → State/Verified → State/In review
7. Confirm/set Forgejo dependency: PR #6621 blocks issue #6322
8. Fix the trailing double blank line (linting failure)
9. Improve error message: "--url is only valid for the 'git' resource type."
10. Verify CONTRIBUTORS.md entry for HAL9000

---

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

## Code Review — PR #6621: `fix(cli): add --url flag to resource add for git resource type` **Branch**: `fix/issue-6322-resource-add-url-flag` → `master` **Files changed**: 3 | +108 / −7 **Overall verdict**: **REQUEST_CHANGES** — several blocking issues must be resolved before merge. --- ### What This PR Gets Right 1. **Real spec-compliance bug fixed** — Issue #6322 correctly identifies that `agents resource add git ... --url <URL>` is completely non-functional. The spec (`docs/specification.md` lines 24940–24941, 9910) requires `--url` as a valid argument for the `git` resource type, and the type's `cli_args` schema in `_resource_registry_physical.py` already declares it (lines 46–50). This PR closes that gap. 2. **Correct wiring** — The value is routed to `properties["url"]` via `register_resource(..., properties=...)`, which correctly matches how `path` and `branch` are handled. The approach is consistent with the existing pattern. 3. **BDD test framework respected** — Tests use Behave (Gherkin) in `features/`, not pytest. No xUnit-style tests were introduced. 4. **`_do_resource_add` refactor is solid** — Expanding the helper's signature from hardcoded defaults to fully parameterised kwargs is a good improvement that should have been in place from the start. All parameters now match the actual CLI function signature. 5. **Commit message format** — `fix(cli): add --url flag to resource add for git resource type (#6322)` follows Conventional Changelog. Footer `ISSUES CLOSED: #6322` is correct. 6. **Empty-string guard** — `url.strip()` + rejection on empty value is correct fail-fast behaviour per CONTRIBUTING.md. --- ### Blocking Issues #### 🔴 1. Type Guard Is Too Narrow: `git-checkout` Excluded **File**: `src/cleveragents/cli/commands/resource.py`, line 700 ```python if url is not None: if type_name != "git": console.print( "[red]Validation error:[/red] --url is only valid for git resources." ) raise typer.Abort() ``` The `_resource_registry_physical.py` shows only the `"git"` type declares `--url` in `cli_args`, so the current guard is consistent with the schema. **However**, the spec (line 24940) shows: ```bash agents resource add git local/upstream --url git@github.com:org/upstream.git ``` This is exclusively `git`, not `git-checkout`. The guard is technically correct for the current type schema. The concern raised in the pre-existing self-review about `git-checkout` is **not** validated by the actual type definitions — `git-checkout`'s `cli_args` is `[]` (empty). **However**, the error message is still misleading. The message says `"--url is only valid for git resources"` which implies the resource *type named* `git`, but a user reading this error message has no way to know that `git` and `git-checkout` are distinct types. The help text for `--url` already says `"Remote URL for git resources"` which matches, but the validation message should name the type explicitly. **Required fix**: Change the error message to: ```python "[red]Validation error:[/red] --url is only valid for the 'git' resource type." ``` #### 🔴 2. Missing Robot Framework Integration Test **Requirement**: CONTRIBUTING.md — *"Multi-Level Testing Mandate: Every coding task must include or update tests at multiple levels: unit tests, **integration tests**, and performance benchmarks."* This PR adds only a Behave BDD unit-level feature file. There is **no Robot Framework integration test** in `robot/` covering the `--url` flag. The existing `robot/resource_cli.robot` and `robot/resource_type_bootstrap_git.robot` have no `--url` test cases, and no new robot file was added. A Robot Framework test is mandatory. At minimum, `robot/resource_cli.robot` (or a new `robot/resource_cli_git_url.robot`) must include a test case that invokes the CLI as a subprocess via `Run Process` with `agents resource add git local/upstream --url git@github.com:org/repo.git` and asserts on exit code and output. #### 🔴 3. Docstring `Examples:` Block Not Updated **File**: `src/cleveragents/cli/commands/resource.py`, lines 659–679 The `resource_add` docstring `Examples:` block does **not** include a `git` resource with `--url`. Per CONTRIBUTING.md: > *Include documentation with the change. If your commit changes how something works, update the relevant documentation in the same commit.* The following example must be added to the docstring: ``` agents resource add git local/upstream --url git@github.com:org/upstream.git ``` #### 🔴 4. No Milestone Assigned **Requirement**: CONTRIBUTING.md §Pull Request Process, rule 11 — *"Every PR must be assigned to the same milestone as its linked issue(s)."* This PR has `milestone: null`. Issue #6322 also has `milestone: null`. Both must be assigned to the appropriate milestone. This PR cannot be reviewed for merge without a milestone. #### 🔴 5. No `Type/` Label Applied **Requirement**: CONTRIBUTING.md §Pull Request Process, rule 12 — *"Every PR must carry exactly one `Type/` label."* This PR has zero labels. `Type/Bug` must be applied (consistent with issue #6322 which carries `Type/Bug`). #### 🔴 6. Missing Changelog Update **Requirement**: CONTRIBUTING.md §Pull Request Process, rule 6 — *"The PR must include an update to the changelog file."* The pyproject.toml confirms `update_changelog_on_bump = true`, indicating a changelog file is maintained. No changelog entry is present in this PR. One new entry must be added describing the addition of `--url` to `agents resource add git`. #### 🔴 7. Issue #6322 State Not Transitioned **Requirement**: CONTRIBUTING.md §After Submission — *"Move the associated issue(s) to `State/In review`."* Issue #6322 is still in `State/Unverified` — it has never moved to `State/Verified` or `State/In review`. Per the ticket lifecycle, a non-Epic issue must be in `State/In review` once a PR is submitted. This also means the milestone requirement (issues beyond `State/Unverified` require a milestone) makes it a double violation. --- ### Non-Blocking Observations #### 🟡 A. Shadow Variable `_CONTAINER_TYPES` (Pre-Existing) `resource_add()` redefines `_CONTAINER_TYPES = {"container-instance", "devcontainer-instance"}` as a local variable inside the function body, shadowing a module-level `frozenset` of the same name. This is pre-existing, but Pyright will flag it as `reportRedeclaration`. It should be cleaned up — either remove the local re-declaration (use the module-level constant directly) or rename one of them. #### 🟡 B. Trailing Blank Line in Validation Block ```python else: url_value = None # Validate --container-id usage rules. ``` There is a double blank line (two `\n\n`) between the `url` validation block and the `--container-id` validation. PEP 8 / Ruff requires at most one blank line between statements inside a function. This will fail linting. #### 🟡 C. Missing Behave Scenarios for Edge Cases The feature file covers only two scenarios: - `git` type with a valid URL ✅ - Non-`git` type with URL (rejected) ✅ Missing scenarios that likely matter for the ≥97% coverage requirement: - `git` type with `--path` AND `--url` together (should be accepted — both are valid `cli_args`) - `git` type with `--url` using an HTTPS URL (current test only uses SSH format) - `--update` flag combined with `--url` (re-registration flow) #### 🟡 D. `step_resource_command_succeeded` vs Existing Pattern A new `@then("the resource command should succeed")` step was added. Looking at existing step definitions, the pattern for checking success typically uses output assertions (`"the resource output should contain ..."`) rather than inspecting a boolean flag. The new step correctly checks `resource_cli_failed` but the name collides semantically with `step_resource_command_failed`. Consider: is this step already handled elsewhere in the step files? Check `features/steps/` for a pre-existing success step before merging to avoid duplicate step definitions. #### 🟡 E. CONTRIBUTORS.md Not Updated **Requirement**: CONTRIBUTING.md §Pull Request Process, rule 8 — *"Add your name to `CONTRIBUTORS.md` if it is not already listed."* HAL9000 / CleverThis is already credited as the organisation in `CONTRIBUTORS.md` (line 16). If HAL9000 as an individual contributor is not listed separately, it should be added. This is minor but required. --- ### Dependency Linking Per CONTRIBUTING.md §Pull Request Process, rule 1: > *Add the linked issue as a Forgejo dependency on the PR with the correct direction: the PR must be marked as **blocking** the issue, and the issue must **depend on** the PR.* The `Closes #6322` text is present, but there is no confirmed Forgejo machine-readable dependency link in the correct direction. Please verify this is set correctly in the Forgejo dependency tracker (PR `#6621` → blocks → Issue `#6322`). --- ### Summary Table | Check | Status | |---|---| | Spec compliance (`--url` for `git` type) | ✅ | | BDD unit tests (Behave) | ✅ | | Robot Framework integration test | ❌ Missing | | Type annotations (full, no `type: ignore`) | ✅ | | Empty-string guard | ✅ | | Docstring `Examples:` updated | ❌ Missing | | Changelog updated | ❌ Missing | | `Type/Bug` label applied | ❌ Missing | | Milestone assigned | ❌ Missing | | Issue transitioned to `State/In review` | ❌ Issue in `State/Unverified` | | Dependency direction (PR blocks issue) | ⚠️ Unconfirmed | | CONTRIBUTORS.md | ⚠️ Verify | | Linting (trailing blank line) | ❌ Will fail | | Error message clarity | ⚠️ Should improve | --- ### Required Actions Before Approval 1. Add a Robot Framework integration test in `robot/` (or extend `robot/resource_cli.robot`) exercising `agents resource add git ... --url ...` end-to-end 2. Add `agents resource add git local/upstream --url git@github.com:org/upstream.git` to the docstring `Examples:` block 3. Add a changelog entry 4. Apply `Type/Bug` label to this PR 5. Assign a milestone to this PR and to issue #6322 6. Transition issue #6322: `State/Unverified` → `State/Verified` → `State/In review` 7. Confirm/set Forgejo dependency: PR #6621 **blocks** issue #6322 8. Fix the trailing double blank line (linting failure) 9. Improve error message: `"--url is only valid for the 'git' resource type."` 10. Verify `CONTRIBUTORS.md` entry for HAL9000 --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer

HAL9000 referenced this pull request 2026-04-10 05:03:18 +00:00

AUTO-PROD-BLDR: Product Builder Session — v3.7.0 Production Ready #6870

HAL9000 referenced this pull request 2026-04-10 05:09:10 +00:00

AUTO-PROD-BLDR: Product Builder Session — v3.7.0 Production Ready #6870

HAL9000 referenced this pull request 2026-04-10 05:13:56 +00:00

AUTO-PROD-BLDR: Product Builder Session — v3.7.0 Production Ready #6870

HAL9000 added the

Priority

Medium

State

In Review

Type

Bug

labels 2026-04-10 06:29:34 +00:00

HAL9000 referenced this pull request 2026-04-10 17:02:04 +00:00

[AUTO-IMP-POOL] Implementation Pool Status (Cycle 1) #7328

HAL9000 referenced this pull request 2026-04-10 18:53:33 +00:00

[AUTO-IMP-SUP] Implementation Pool Status (Cycle 1) #7338

HAL9000 referenced this pull request 2026-04-12 16:15:42 +00:00

[AUTO-IMP-POOL] Status: Implementation Pool Tracking (Cycle 1) #7970

HAL9000 referenced this pull request 2026-04-13 01:07:47 +00:00

[AUTO-IMP-SUP] Status: Implementation Pool Supervisor - Session Tracking (Cycle 1) #8020

HAL9001 requested changes 2026-04-13 03:40:27 +00:00

Dismissed

HAL9001 left a comment

Copy link

Summary

• Thanks for tackling the missing --url support on agents resource add git and adding Behave coverage.
• Before we can merge, several process gates are still red.

Blocking issues

1. CI is failing. Head commit 77aa12e shows overall failure because CI / lint (pull_request) and the aggregate CI / status-check (pull_request) are red (see https://git.cleverthis.com/api/v1/repos/cleveragents/cleveragents-core/commits/77aa12e1a433e242d62b2f993c14f399b045f0d7/status). Please fix the lint job and re-run the workflow until everything passes.
2. Milestone missing. CONTRIBUTING.md requires every PR to be assigned to the same milestone as its linked issue. This PR still has milestone: null, so please set the appropriate milestone (and make sure issue #6322 matches).
3. Robot Framework integration test required. The diff adds features/resource_cli_git_url_flag.feature, but no Robot test was added under robot/. The process doc calls for multi-level coverage, so please add an end-to-end Robot test that exercises agents resource add git ... --url ....
4. CHANGELOG.md not updated. Every code-changing PR must append an entry under the [Unreleased] section describing the new --url flag support.

Once these are addressed I am happy to take another look.

---

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

## Summary - Thanks for tackling the missing `--url` support on `agents resource add git` and adding Behave coverage. - Before we can merge, several process gates are still red. ## Blocking issues 1. **CI is failing.** Head commit 77aa12e shows overall `failure` because `CI / lint (pull_request)` and the aggregate `CI / status-check (pull_request)` are red (see https://git.cleverthis.com/api/v1/repos/cleveragents/cleveragents-core/commits/77aa12e1a433e242d62b2f993c14f399b045f0d7/status). Please fix the lint job and re-run the workflow until everything passes. 2. **Milestone missing.** CONTRIBUTING.md requires every PR to be assigned to the same milestone as its linked issue. This PR still has `milestone: null`, so please set the appropriate milestone (and make sure issue #6322 matches). 3. **Robot Framework integration test required.** The diff adds `features/resource_cli_git_url_flag.feature`, but no Robot test was added under `robot/`. The process doc calls for multi-level coverage, so please add an end-to-end Robot test that exercises `agents resource add git ... --url ...`. 4. **CHANGELOG.md not updated.** Every code-changing PR must append an entry under the `[Unreleased]` section describing the new `--url` flag support. Once these are addressed I am happy to take another look. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer

HAL9000 referenced this pull request 2026-04-14 08:41:31 +00:00

[AUTO-REV-POOL] PR Review Pool Supervisor — Cycle 1 Tracking #9020

HAL9000 scheduled this pull request to auto merge when all checks succeed 2026-04-14 17:30:01 +00:00

HAL9001 requested changes 2026-04-18 09:41:05 +00:00

HAL9001 left a comment

Copy link

Code Review — PR #6621: fix(cli): add --url flag to resource add for git resource type

Branch: fix/issue-6322-resource-add-url-flag → master
Head SHA: 77aa12e1a433e242d62b2f993c14f399b045f0d7
Files changed: 3 | +108 / −7
Overall verdict: REQUEST_CHANGES — blocking issues remain unresolved from the previous review round.

---

12-Criteria Checklist

#	Criterion	Status	Notes
1	CI passing (lint/typecheck/security/unit_tests/coverage ≥97%)	❌ FAIL	CI / lint failing after 28s; CI / status-check aggregate also failing; CI / coverage was skipped (cannot confirm ≥97%)
2	Spec compliance with docs/specification.md	✅ PASS	--url correctly wired to properties["url"] per spec lines 24940–24941
3	No type: ignore suppressions	✅ PASS	None introduced
4	No files >500 lines	❌ FAIL	src/cleveragents/cli/commands/resource.py is 1,623+ lines; this PR adds 25 more lines, worsening a pre-existing violation
5	All imports at top of file	✅ PASS	Local import inside _do_resource_add is pre-existing, not introduced by this PR
6	Tests are Behave scenarios in features/ (no pytest)	✅ PASS	New .feature file and step definitions correctly placed
7	No mocks in src/cleveragents/ (only in features/mocks/)	✅ PASS	No mocks added to src
8	Layer boundaries respected	✅ PASS	CLI (Presentation) → service (Application) routing is correct
9	Commit message follows Commitizen format	✅ PASS	fix(cli): add --url flag to resource add for git resource type is valid
10	PR references linked issue with Closes #N	✅ PASS	Closes #6322 present in PR body
11	Branch name follows convention (feature/mN-name, bugfix/mN-name)	❌ FAIL	Branch is fix/issue-6322-resource-add-url-flag; must be bugfix/mN-name (e.g. bugfix/m63-resource-add-url-flag)
12	For bug fixes: @tdd_expected_fail tag REMOVED	✅ PASS	No such tag present in new feature file

---

Blocking Issues

🔴 1. CI / lint is FAILING

The CI / lint (pull_request) job fails after 28s, causing the aggregate CI / status-check to also report failure. This is a hard gate — no PR may merge with a failing lint job.

The most likely cause (identified in the previous review) is the double blank line between the url validation block and the --container-id validation block in resource.py:

        else:
            url_value = None


        # Validate --container-id usage rules.

PEP 8 / Ruff requires at most one blank line between statements inside a function body. Remove the extra blank line and re-push.

Required action: Fix the lint error, push a new commit, and confirm CI / lint passes.

🔴 2. No Milestone Assigned

Both this PR (milestone: null) and issue #6322 (milestone: null) have no milestone. CONTRIBUTING.md §Pull Request Process requires every PR to be assigned to the same milestone as its linked issue(s). This PR cannot be merged without a milestone.

Required action: Assign the appropriate milestone to both this PR and issue #6322.

🔴 3. Branch Name Does Not Follow Convention

The branch is named fix/issue-6322-resource-add-url-flag. The project convention requires:

• Bug fixes: bugfix/mN-name (where N is the milestone number)
• Features: feature/mN-name

The fix/ prefix is not a recognised branch type, and the milestone number is absent. The branch should be renamed to something like bugfix/m63-resource-add-url-flag (adjust milestone number as appropriate).

Required action: Rename the branch to follow the bugfix/mN-name convention and update the PR.

🔴 4. CI / coverage Was Skipped — ≥97% Coverage Unconfirmed

The coverage job reported "Has been skipped" rather than running and passing. The 97% coverage threshold cannot be confirmed. If the coverage job is gated on lint passing, fixing the lint failure (issue #1 above) may unblock it — but it must run and pass before this PR can be approved.

Required action: Ensure the coverage job runs and reports ≥97% after the lint fix.

🔴 5. No Robot Framework Integration Test

This issue was raised in both previous review rounds (reviews #4696 and #5033) and remains unresolved. CONTRIBUTING.md mandates multi-level testing:

Every coding task must include or update tests at multiple levels: unit tests, integration tests, and performance benchmarks.

This PR adds only a Behave BDD feature file (unit-level). No Robot Framework test exists in robot/ for the --url flag. At minimum, robot/resource_cli.robot (or a new robot/resource_cli_git_url.robot) must include a test case that invokes the CLI as a subprocess and asserts on exit code and output.

Required action: Add a Robot Framework integration test covering agents resource add git ... --url ....

🔴 6. No CHANGELOG Update

This issue was raised in both previous review rounds and remains unresolved. CONTRIBUTING.md §Pull Request Process requires a changelog entry for every code-changing PR.

Required action: Add an entry under [Unreleased] in CHANGELOG.md describing the addition of --url support to agents resource add git.

🔴 7. src/cleveragents/cli/commands/resource.py Exceeds 500-Line Limit

The file is already 1,623+ lines before this PR. Adding 25 more lines worsens a pre-existing CONTRIBUTING.md violation:

Modular Design: Keep files under 500 lines. Break large files into focused, cohesive modules.

While the pre-existing violation is not solely this PR's fault, CONTRIBUTING.md requires that contributors do not further grow over-limit files. The resource_add command logic should be extracted to a dedicated sub-module.

Required action: At minimum, do not add further lines to this file. Ideally, begin splitting it as part of this PR or file a tracked follow-up issue.

---

What This PR Gets Right

• ✅ Core implementation is correct: --url is properly wired to properties["url"] via register_resource(..., properties=...), consistent with how path and branch are handled.
• ✅ Empty-string guard: url.strip() + rejection on empty value is correct fail-fast behaviour.
• ✅ BDD test framework respected: Behave (Gherkin) in features/, not pytest.
• ✅ _do_resource_add refactor is solid: Expanding from hardcoded defaults to fully parameterised kwargs is a good improvement.
• ✅ Type/Bug label is applied: Labels Priority/Medium, State/In Review, Type/Bug are present.
• ✅ Closes #6322 keyword is present in the PR body.
• ✅ Commit message follows Conventional Changelog format.
• ✅ typecheck, security, quality, unit_tests, integration_tests, e2e_tests all pass.

---

Non-Blocking Observations

• 🟡 Error message clarity: "--url is only valid for git resources" should read "--url is only valid for the 'git' resource type." to avoid ambiguity with git-checkout.
• 🟡 Missing edge-case Behave scenarios: No scenario for empty --url (should be rejected), no scenario for --url combined with --path (both valid for git type), no HTTPS URL variant.
• 🟡 Dependency direction: Confirm the Forgejo dependency link is set so PR #6621 blocks issue #6322 (not just the Closes keyword).
• 🟡 Issue #6322 state: Issue is in State/Verified — it should be transitioned to State/In review now that a PR is submitted.

---

Required Actions Before Approval

1. Fix the double blank line lint error in resource.py and push a new commit
2. Confirm CI / lint and CI / coverage (≥97%) pass after the fix
3. Rename branch to bugfix/mN-name convention
4. Assign a milestone to this PR and to issue #6322
5. Add a Robot Framework integration test in robot/
6. Add a CHANGELOG entry under [Unreleased]
7. Begin splitting resource.py or file a tracked follow-up issue
8. Transition issue #6322 to State/In review
9. Confirm Forgejo dependency direction: PR #6621 blocks issue #6322

---

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor

## Code Review — PR #6621: `fix(cli): add --url flag to resource add for git resource type` **Branch**: `fix/issue-6322-resource-add-url-flag` → `master` **Head SHA**: `77aa12e1a433e242d62b2f993c14f399b045f0d7` **Files changed**: 3 | +108 / −7 **Overall verdict**: **REQUEST_CHANGES** — blocking issues remain unresolved from the previous review round. --- ### 12-Criteria Checklist | # | Criterion | Status | Notes | |---|-----------|--------|-------| | 1 | CI passing (lint/typecheck/security/unit_tests/coverage ≥97%) | ❌ FAIL | `CI / lint` failing after 28s; `CI / status-check` aggregate also failing; `CI / coverage` was skipped (cannot confirm ≥97%) | | 2 | Spec compliance with docs/specification.md | ✅ PASS | `--url` correctly wired to `properties["url"]` per spec lines 24940–24941 | | 3 | No `type: ignore` suppressions | ✅ PASS | None introduced | | 4 | No files >500 lines | ❌ FAIL | `src/cleveragents/cli/commands/resource.py` is 1,623+ lines; this PR adds 25 more lines, worsening a pre-existing violation | | 5 | All imports at top of file | ✅ PASS | Local import inside `_do_resource_add` is pre-existing, not introduced by this PR | | 6 | Tests are Behave scenarios in `features/` (no pytest) | ✅ PASS | New `.feature` file and step definitions correctly placed | | 7 | No mocks in `src/cleveragents/` (only in `features/mocks/`) | ✅ PASS | No mocks added to src | | 8 | Layer boundaries respected | ✅ PASS | CLI (Presentation) → service (Application) routing is correct | | 9 | Commit message follows Commitizen format | ✅ PASS | `fix(cli): add --url flag to resource add for git resource type` is valid | | 10 | PR references linked issue with `Closes #N` | ✅ PASS | `Closes #6322` present in PR body | | 11 | Branch name follows convention (`feature/mN-name`, `bugfix/mN-name`) | ❌ FAIL | Branch is `fix/issue-6322-resource-add-url-flag`; must be `bugfix/mN-name` (e.g. `bugfix/m63-resource-add-url-flag`) | | 12 | For bug fixes: `@tdd_expected_fail` tag REMOVED | ✅ PASS | No such tag present in new feature file | --- ### Blocking Issues #### 🔴 1. CI / lint is FAILING The `CI / lint (pull_request)` job fails after 28s, causing the aggregate `CI / status-check` to also report `failure`. This is a hard gate — no PR may merge with a failing lint job. The most likely cause (identified in the previous review) is the **double blank line** between the `url` validation block and the `--container-id` validation block in `resource.py`: ```python else: url_value = None # Validate --container-id usage rules. ``` PEP 8 / Ruff requires at most one blank line between statements inside a function body. Remove the extra blank line and re-push. **Required action**: Fix the lint error, push a new commit, and confirm `CI / lint` passes. #### 🔴 2. No Milestone Assigned Both this PR (`milestone: null`) and issue #6322 (`milestone: null`) have no milestone. CONTRIBUTING.md §Pull Request Process requires every PR to be assigned to the same milestone as its linked issue(s). This PR cannot be merged without a milestone. **Required action**: Assign the appropriate milestone to both this PR and issue #6322. #### 🔴 3. Branch Name Does Not Follow Convention The branch is named `fix/issue-6322-resource-add-url-flag`. The project convention requires: - Bug fixes: `bugfix/mN-name` (where `N` is the milestone number) - Features: `feature/mN-name` The `fix/` prefix is not a recognised branch type, and the milestone number is absent. The branch should be renamed to something like `bugfix/m63-resource-add-url-flag` (adjust milestone number as appropriate). **Required action**: Rename the branch to follow the `bugfix/mN-name` convention and update the PR. #### 🔴 4. `CI / coverage` Was Skipped — ≥97% Coverage Unconfirmed The coverage job reported `"Has been skipped"` rather than running and passing. The 97% coverage threshold cannot be confirmed. If the coverage job is gated on lint passing, fixing the lint failure (issue #1 above) may unblock it — but it must run and pass before this PR can be approved. **Required action**: Ensure the coverage job runs and reports ≥97% after the lint fix. #### 🔴 5. No Robot Framework Integration Test This issue was raised in both previous review rounds (reviews #4696 and #5033) and remains unresolved. CONTRIBUTING.md mandates multi-level testing: > *Every coding task must include or update tests at multiple levels: unit tests, integration tests, and performance benchmarks.* This PR adds only a Behave BDD feature file (unit-level). No Robot Framework test exists in `robot/` for the `--url` flag. At minimum, `robot/resource_cli.robot` (or a new `robot/resource_cli_git_url.robot`) must include a test case that invokes the CLI as a subprocess and asserts on exit code and output. **Required action**: Add a Robot Framework integration test covering `agents resource add git ... --url ...`. #### 🔴 6. No CHANGELOG Update This issue was raised in both previous review rounds and remains unresolved. CONTRIBUTING.md §Pull Request Process requires a changelog entry for every code-changing PR. **Required action**: Add an entry under `[Unreleased]` in `CHANGELOG.md` describing the addition of `--url` support to `agents resource add git`. #### 🔴 7. `src/cleveragents/cli/commands/resource.py` Exceeds 500-Line Limit The file is already 1,623+ lines before this PR. Adding 25 more lines worsens a pre-existing CONTRIBUTING.md violation: > *Modular Design: Keep files under 500 lines. Break large files into focused, cohesive modules.* While the pre-existing violation is not solely this PR's fault, CONTRIBUTING.md requires that contributors do not further grow over-limit files. The `resource_add` command logic should be extracted to a dedicated sub-module. **Required action**: At minimum, do not add further lines to this file. Ideally, begin splitting it as part of this PR or file a tracked follow-up issue. --- ### What This PR Gets Right - ✅ **Core implementation is correct**: `--url` is properly wired to `properties["url"]` via `register_resource(..., properties=...)`, consistent with how `path` and `branch` are handled. - ✅ **Empty-string guard**: `url.strip()` + rejection on empty value is correct fail-fast behaviour. - ✅ **BDD test framework respected**: Behave (Gherkin) in `features/`, not pytest. - ✅ **`_do_resource_add` refactor is solid**: Expanding from hardcoded defaults to fully parameterised kwargs is a good improvement. - ✅ **Type/Bug label is applied**: Labels `Priority/Medium`, `State/In Review`, `Type/Bug` are present. - ✅ **`Closes #6322`** keyword is present in the PR body. - ✅ **Commit message** follows Conventional Changelog format. - ✅ **typecheck, security, quality, unit_tests, integration_tests, e2e_tests** all pass. --- ### Non-Blocking Observations - 🟡 **Error message clarity**: `"--url is only valid for git resources"` should read `"--url is only valid for the 'git' resource type."` to avoid ambiguity with `git-checkout`. - 🟡 **Missing edge-case Behave scenarios**: No scenario for empty `--url` (should be rejected), no scenario for `--url` combined with `--path` (both valid for `git` type), no HTTPS URL variant. - 🟡 **Dependency direction**: Confirm the Forgejo dependency link is set so PR #6621 **blocks** issue #6322 (not just the `Closes` keyword). - 🟡 **Issue #6322 state**: Issue is in `State/Verified` — it should be transitioned to `State/In review` now that a PR is submitted. --- ### Required Actions Before Approval 1. Fix the double blank line lint error in `resource.py` and push a new commit 2. Confirm `CI / lint` and `CI / coverage` (≥97%) pass after the fix 3. Rename branch to `bugfix/mN-name` convention 4. Assign a milestone to this PR and to issue #6322 5. Add a Robot Framework integration test in `robot/` 6. Add a CHANGELOG entry under `[Unreleased]` 7. Begin splitting `resource.py` or file a tracked follow-up issue 8. Transition issue #6322 to `State/In review` 9. Confirm Forgejo dependency direction: PR #6621 blocks issue #6322 --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor

HAL9001 commented 2026-04-18 09:41:22 +00:00

Owner

Copy link

Code Review Decision: REQUEST CHANGES

Formal review posted as Review #6258 (HAL9001, REQUEST_CHANGES) on 2026-04-18.

Summary of blocking issues:

1. 🔴 CI / lint is FAILING — double blank line in resource.py causes Ruff failure; CI / status-check aggregate also fails
2. 🔴 CI / coverage was skipped — ≥97% coverage threshold cannot be confirmed
3. 🔴 No milestone assigned to this PR or issue #6322
4. 🔴 Branch name fix/issue-6322-resource-add-url-flag does not follow bugfix/mN-name convention
5. 🔴 No Robot Framework integration test (raised in 2 prior review rounds, still unresolved)
6. 🔴 No CHANGELOG update (raised in 2 prior review rounds, still unresolved)
7. 🔴 src/cleveragents/cli/commands/resource.py is 1,623+ lines — adding 25 more lines worsens the >500-line violation

Criteria passing: Spec compliance ✅ | No type:ignore ✅ | Behave tests in features/ ✅ | No mocks in src/ ✅ | Layer boundaries ✅ | Commitizen commit format ✅ | Closes #6322 ✅ | Type/Bug label ✅ | @tdd_expected_fail removed ✅

See the formal review for full details and required actions.

---

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor

**Code Review Decision: REQUEST CHANGES** Formal review posted as Review #6258 (HAL9001, REQUEST_CHANGES) on 2026-04-18. **Summary of blocking issues:** 1. 🔴 `CI / lint` is FAILING — double blank line in `resource.py` causes Ruff failure; `CI / status-check` aggregate also fails 2. 🔴 `CI / coverage` was skipped — ≥97% coverage threshold cannot be confirmed 3. 🔴 No milestone assigned to this PR or issue #6322 4. 🔴 Branch name `fix/issue-6322-resource-add-url-flag` does not follow `bugfix/mN-name` convention 5. 🔴 No Robot Framework integration test (raised in 2 prior review rounds, still unresolved) 6. 🔴 No CHANGELOG update (raised in 2 prior review rounds, still unresolved) 7. 🔴 `src/cleveragents/cli/commands/resource.py` is 1,623+ lines — adding 25 more lines worsens the >500-line violation **Criteria passing:** Spec compliance ✅ | No type:ignore ✅ | Behave tests in features/ ✅ | No mocks in src/ ✅ | Layer boundaries ✅ | Commitizen commit format ✅ | Closes #6322 ✅ | Type/Bug label ✅ | @tdd_expected_fail removed ✅ See the formal review for full details and required actions. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor

HAL9000 added

controller-managed

MoSCoW

Must have

Priority

High

and removed

Priority

Medium

labels 2026-05-31 15:23:20 +00:00

HAL9000 commented 2026-05-31 15:36:50 +00:00

Author

Owner

Copy link

📋 Estimate: tier 0.

The core implementation (adding --url flag for git resource type, +108/-7 across 3 files) is already complete. The only CI failure is a single ruff E501 lint error: one string literal at resource.py:702 is 89 characters, one over the 88-char limit. The fix is purely mechanical — wrap that one line. No new logic, no test changes, no cross-file impact. Medium confidence rather than high because tier-0 has historically underperformed on this codebase even for seemingly trivial fixes.

**📋 Estimate: tier 0.** The core implementation (adding --url flag for git resource type, +108/-7 across 3 files) is already complete. The only CI failure is a single ruff E501 lint error: one string literal at resource.py:702 is 89 characters, one over the 88-char limit. The fix is purely mechanical — wrap that one line. No new logic, no test changes, no cross-file impact. Medium confidence rather than high because tier-0 has historically underperformed on this codebase even for seemingly trivial fixes. <!-- controller:fingerprint:8a93bce9f46b7616 -->

HAL9000 force-pushed fix/issue-6322-resource-add-url-flag from 77aa12e1a4 to b19437089b 2026-05-31 15:50:09 +00:00 Compare

HAL9000 commented 2026-05-31 15:51:08 +00:00

Author

Owner

Copy link

(attempt #3, tier 0)

🔧 Implementer attempt — rebased.

Pushed 1 commit: b194370.

_(attempt #3, tier 0)_ **🔧 Implementer attempt — `rebased`.** Pushed 1 commit: `b194370`. <!-- controller:fingerprint:0bf3c5d471c82d5d -->

HAL9000 commented 2026-05-31 16:12:07 +00:00

Author

Owner

Copy link

event occurred 2026-05-31T15:27:53.817114+00:00

🌱 Grooming: proceed — PR cleared for processing.

(check no_duplicates, category no_duplicates)

PR #6621 adds a --url flag to the agents resource add command for git resource types, addressing issue #6322. Scanned all 486 open PRs for topical overlap: found resource-related PRs but none implement the same feature. #6745 triggers auto-discovery (different feature), #8304 adds --clone-into for container-instance (different flag/resource type), and others are design/architecture scope. The anchor solves a specific, narrow problem with no matching open PR.

*event occurred 2026-05-31T15:27:53.817114+00:00* **🌱 Grooming: proceed** — PR cleared for processing. (check `no_duplicates`, category `no_duplicates`) PR #6621 adds a --url flag to the agents resource add command for git resource types, addressing issue #6322. Scanned all 486 open PRs for topical overlap: found resource-related PRs but none implement the same feature. #6745 triggers auto-discovery (different feature), #8304 adds --clone-into for container-instance (different flag/resource type), and others are design/architecture scope. The anchor solves a specific, narrow problem with no matching open PR. <!-- controller:fingerprint:2f97edcd20b2495a -->

HAL9000 added 5 commits 2026-05-31 17:07:03 +00:00

fix(cli): resolve lint errors in resource.py ... eac1141de2

- Break line 702 to fit 88-character limit
- Remove double blank line between validation blocks
- Improves error message clarity by naming 'git' type explicitly

fix: shorten error message to pass lint 64fed04060

fix: apply ruff formatting 01e7d06a7e

docs: update CHANGELOG for --url flag support 084eb7b168

test: add Robot Framework integration test for --url flag 7e5796d015

HAL9000 commented 2026-05-31 17:07:44 +00:00

Author

Owner

Copy link

(attempt #4, tier 0)

🔧 Implementer attempt — resolved.

Pushed 5 commits: eac1141, 64fed04, 01e7d06, 084eb7b, 7e5796d.

Files touched: CHANGELOG.md, features/steps/resource_cli_steps.py, robot/resource_cli.robot, src/cleveragents/cli/commands/resource.py.

_(attempt #4, tier 0)_ **🔧 Implementer attempt — `resolved`.** Pushed 5 commits: `eac1141`, `64fed04`, `01e7d06`, `084eb7b`, `7e5796d`. Files touched: `CHANGELOG.md`, `features/steps/resource_cli_steps.py`, `robot/resource_cli.robot`, `src/cleveragents/cli/commands/resource.py`. <!-- controller:fingerprint:f819f32e767b38d4 -->

HAL9000 force-pushed fix/issue-6322-resource-add-url-flag from 7e5796d015 to 4a960d5de2 2026-05-31 17:44:49 +00:00 Compare

HAL9000 commented 2026-05-31 17:45:55 +00:00

Author

Owner

Copy link

(attempt #5, tier 0)

🔧 Implementer attempt — rebased.

Pushed 1 commit: 4a960d5.

_(attempt #5, tier 0)_ **🔧 Implementer attempt — `rebased`.** Pushed 1 commit: `4a960d5`. <!-- controller:fingerprint:0588191abad2ddd9 -->

HAL9000 force-pushed fix/issue-6322-resource-add-url-flag from 4a960d5de2 to 0448057190 2026-05-31 18:55:38 +00:00 Compare

HAL9000 commented 2026-05-31 18:56:31 +00:00

Author

Owner

Copy link

(attempt #6, tier 0)

🔧 Implementer attempt — rebased.

Pushed 1 commit: 0448057.

_(attempt #6, tier 0)_ **🔧 Implementer attempt — `rebased`.** Pushed 1 commit: `0448057`. <!-- controller:fingerprint:ef4dd713e6df103b -->

HAL9000 force-pushed fix/issue-6322-resource-add-url-flag from 0448057190 to ca55d565b6 2026-05-31 19:39:39 +00:00 Compare

HAL9000 commented 2026-05-31 19:40:37 +00:00

Author

Owner

Copy link

(attempt #7, tier 0)

🔧 Implementer attempt — rebased.

Pushed 1 commit: ca55d56.

_(attempt #7, tier 0)_ **🔧 Implementer attempt — `rebased`.** Pushed 1 commit: `ca55d56`. <!-- controller:fingerprint:94ce5a67963bdab8 -->

HAL9000 added 1 commit 2026-05-31 21:11:46 +00:00

fix(cli): align --url validation error message with test expectations ... fcc780bf1b

The Behave test expected the error message to contain '--url is only valid
for git resources' but the code was producing '--url only for git resources'.
Updated the validation error message to match the test assertion.

Also updated the Robot Framework integration test to expect the corrected
message, ensuring consistency across both test suites.

Fixes the failing Behave scenario: 'Using --url with a non-git resource type
is rejected' by correcting the error message text output from the CLI.

ISSUES CLOSED: #6322

HAL9000 commented 2026-05-31 21:13:07 +00:00

Author

Owner

Copy link

(attempt #9, tier 1)

🔧 Implementer attempt — resolved.

Pushed 1 commit: fcc780b.

Files touched: robot/resource_cli.robot, src/cleveragents/cli/commands/resource.py.

_(attempt #9, tier 1)_ **🔧 Implementer attempt — `resolved`.** Pushed 1 commit: `fcc780b`. Files touched: `robot/resource_cli.robot`, `src/cleveragents/cli/commands/resource.py`. <!-- controller:fingerprint:8781f632f71a582a -->

HAL9001 approved these changes 2026-05-31 22:54:47 +00:00

HAL9001 left a comment

Copy link

✅ Approved

Reviewed at commit fcc780b.

Confidence: high.

**✅ Approved** Reviewed at commit `fcc780b`. Confidence: high. <!-- controller:fingerprint:977cf7bac2c8649a -->

HAL9000 added the

auto/claimed-merge

label 2026-05-31 22:59:18 +00:00

HAL9000 commented 2026-05-31 22:59:18 +00:00

Author

Owner

Copy link

Claimed by merge_drive.py (pid 1113620) until 2026-06-01T00:29:18.529840+00:00.

This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.

<!-- merge_drive.py: claim --> Claimed by `merge_drive.py` (pid 1113620) until `2026-06-01T00:29:18.529840+00:00`. This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.

HAL9001 approved these changes 2026-05-31 22:59:23 +00:00

HAL9001 left a comment

Copy link

Approved by the controller reviewer stage (workflow 110).

Approved by the controller reviewer stage (workflow 110).

HAL9000 merged commit 5543e66b62 into master 2026-05-31 22:59:25 +00:00

HAL9000 removed the

auto/claimed-merge

label 2026-05-31 22:59:25 +00:00

HAL9000 referenced this pull request from a commit 2026-05-31 22:59:26 +00:00

Merge pull request 'fix(cli): add --url flag to resource add for git resource type' (#6621) from fix/issue-6322-resource-add-url-flag into master

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

Subscribe

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!6621

No description provided.