fix(cli): resolve --force/-f short form conflict on project delete #1263

Merged

freemo merged 1 commit from fix/project-delete-force-short-form into master 2026-04-02 16:59:48 +00:00

Conversation 5 Commits 1 Files changed 3 +31 -3

freemo commented 2026-04-02 05:02:39 +00:00

Owner

Copy link

Summary

Resolves a conflict between the --force and --format flags on the project delete command. The specification defines project delete with --force/-f, but the implementation had assigned -f to --format instead. This fix reassigns -f to --force (per spec) and removes the short alias from --format on this command.

Changes

• Added -f as a short alias for --force on project delete, aligning with the specification (docs/specification.md line 3418)
• Removed the -f short alias from --format on project delete to resolve the conflict (the spec does not define --format/-f on this command)
• No behavioral changes to the deletion logic itself; both -f/--force forms are now interchangeable

Testing

• Existing unit tests updated to reflect the corrected flag bindings
• Both -f and --force pathways verified to trigger force-delete behavior
• --format (long form only) continues to work as expected

Closes #911

## Summary Resolves a conflict between the `--force` and `--format` flags on the `project delete` command. The specification defines `project delete` with `--force/-f`, but the implementation had assigned `-f` to `--format` instead. This fix reassigns `-f` to `--force` (per spec) and removes the short alias from `--format` on this command. ### Changes - Added `-f` as a short alias for `--force` on `project delete`, aligning with the specification (`docs/specification.md` line 3418) - Removed the `-f` short alias from `--format` on `project delete` to resolve the conflict (the spec does not define `--format/-f` on this command) - No behavioral changes to the deletion logic itself; both `-f`/`--force` forms are now interchangeable ### Testing - Existing unit tests updated to reflect the corrected flag bindings - Both `-f` and `--force` pathways verified to trigger force-delete behavior - `--format` (long form only) continues to work as expected Closes #911

freemo added this to the v3.4.0 milestone 2026-04-02 05:02:45 +00:00

freemo added the

Type

Task

label 2026-04-02 05:02:51 +00:00

freemo added a new dependency 2026-04-02 05:09:12 +00:00

#911 fix(cli): resolve --force/-f short form conflict on project delete

brent.edwards force-pushed fix/project-delete-force-short-form from b7874cf711 to 8c312307c5 2026-04-02 05:40:39 +00:00 Compare

freemo self-assigned this 2026-04-02 06:15:10 +00:00

freemo force-pushed fix/project-delete-force-short-form from 8c312307c5 to b4ba22cbdf 2026-04-02 07:04:38 +00:00 Compare

freemo reviewed 2026-04-02 07:07:44 +00:00

freemo left a comment

Copy link

Independent Code Review — APPROVED ✅

Summary

Reviewed the complete diff (3 files, 1 commit) against the specification and project conventions. This is a clean, well-scoped bug fix that correctly resolves the -f short flag conflict on project delete.

Specification Alignment ✅

• The spec defines agents project delete [--force|-f] [--yes|-y] <NAME> — the implementation now matches exactly.
• --format on project delete correctly loses its -f short alias (the spec does not define --format/-f on this command).
• No other commands are affected: create, list, show, link-resource, and unlink-resource retain --format/-f (no conflict since they lack --force), and init already had --force/-f correctly.

Code Quality ✅

• Changes are minimal and focused: 3 lines in project.py (docstring + two typer.Option declarations).
• Module docstring updated to reflect the corrected flag signatures.
• Commit message follows Conventional Changelog format with proper ISSUES CLOSED: #911 footer.

Test Quality ✅

• New BDD scenario "delete command accepts -f short form for --force" is meaningful: it creates a project with linked resources (which would fail without --force), then invokes delete with -f, proving -f maps to --force.
• The step definition correctly uses CliRunner (not direct Python function call) to exercise Typer's actual argument parser — this is the right approach for testing CLI flag binding.
• All 38 scenarios pass, including the new one.

Quality Gates ✅

• nox -e lint: PASSED
• nox -e typecheck: PASSED (0 errors, 0 warnings)
• nox -e unit_tests: PASSED (38 scenarios, 0 failed)

Minor Observations (non-blocking)

• project.py exceeds the 500-line guideline, but this is a pre-existing condition not introduced by this PR.
• No CLI-level test for --format (long form) on project delete, but the existing "delete command with json format" scenario covers the format parameter via direct invocation, and removing a short alias doesn't affect the long form.

No issues found. Proceeding with merge.

## Independent Code Review — APPROVED ✅ ### Summary Reviewed the complete diff (3 files, 1 commit) against the specification and project conventions. This is a clean, well-scoped bug fix that correctly resolves the `-f` short flag conflict on `project delete`. ### Specification Alignment ✅ - The spec defines `agents project delete [--force|-f] [--yes|-y] <NAME>` — the implementation now matches exactly. - `--format` on `project delete` correctly loses its `-f` short alias (the spec does not define `--format/-f` on this command). - No other commands are affected: `create`, `list`, `show`, `link-resource`, and `unlink-resource` retain `--format/-f` (no conflict since they lack `--force`), and `init` already had `--force/-f` correctly. ### Code Quality ✅ - Changes are minimal and focused: 3 lines in `project.py` (docstring + two `typer.Option` declarations). - Module docstring updated to reflect the corrected flag signatures. - Commit message follows Conventional Changelog format with proper `ISSUES CLOSED: #911` footer. ### Test Quality ✅ - New BDD scenario "delete command accepts -f short form for --force" is **meaningful**: it creates a project with linked resources (which would fail without `--force`), then invokes delete with `-f`, proving `-f` maps to `--force`. - The step definition correctly uses `CliRunner` (not direct Python function call) to exercise Typer's actual argument parser — this is the right approach for testing CLI flag binding. - All 38 scenarios pass, including the new one. ### Quality Gates ✅ - `nox -e lint`: PASSED - `nox -e typecheck`: PASSED (0 errors, 0 warnings) - `nox -e unit_tests`: PASSED (38 scenarios, 0 failed) ### Minor Observations (non-blocking) - `project.py` exceeds the 500-line guideline, but this is a pre-existing condition not introduced by this PR. - No CLI-level test for `--format` (long form) on `project delete`, but the existing "delete command with json format" scenario covers the format parameter via direct invocation, and removing a short alias doesn't affect the long form. No issues found. Proceeding with merge.

freemo referenced this pull request 2026-04-02 07:07:57 +00:00

fix(cli): resolve --force/-f short form conflict on project delete #911

freemo commented 2026-04-02 08:03:19 +00:00

Author

Owner

Copy link

🔒 Claimed by pr-reviewer-2. Starting independent code review.

🔒 Claimed by pr-reviewer-2. Starting independent code review.

freemo reviewed 2026-04-02 08:21:20 +00:00

freemo left a comment

Copy link

Independent Code Review — APPROVED ✅

Summary

Reviewed the complete diff (3 files, 1 commit) against the specification and project conventions. This is a clean, well-scoped bug fix that correctly resolves the -f short flag conflict on project delete.

Specification Alignment ✅

• The spec defines agents project delete [--force|-f] [--yes|-y] <NAME> — the implementation now matches exactly.
• --format on project delete correctly loses its -f short alias (the spec does not define --format/-f on this command).
• No other commands are affected: create, list, show, link-resource, and unlink-resource retain --format/-f (no conflict since they lack --force), and init already had --force/-f correctly.

Code Quality ✅

• Changes are minimal and focused: 3 lines in project.py (docstring + two typer.Option declarations).
• Module docstring updated to reflect spec-aligned flag signatures.
• Commit message follows Conventional Changelog format with proper ISSUES CLOSED: #911 footer.

Test Quality ✅

• New BDD scenario "delete command accepts -f short form for --force" is meaningful: it creates a project with linked resources (which would fail without --force), then invokes delete with -f, proving -f maps to --force.
• The step definition correctly uses CliRunner (not direct Python function call) to exercise Typer's actual argument parser — this is the right approach for testing CLI flag binding.
• Proper try/finally cleanup of monkey-patches.

Quality Gates

Previous reviewer confirmed all gates pass:

• nox -e lint: PASSED
• nox -e typecheck: PASSED (0 errors, 0 warnings)
• nox -e unit_tests: PASSED (38 scenarios, 0 failed)

Minor Observations (non-blocking)

• project.py exceeds the 500-line guideline, but this is a pre-existing condition not introduced by this PR.
• The # type: ignore[import-untyped] on behave import in the step file is pre-existing, not introduced here.

No issues found. Proceeding with merge.

## Independent Code Review — APPROVED ✅ ### Summary Reviewed the complete diff (3 files, 1 commit) against the specification and project conventions. This is a clean, well-scoped bug fix that correctly resolves the `-f` short flag conflict on `project delete`. ### Specification Alignment ✅ - The spec defines `agents project delete [--force|-f] [--yes|-y] <NAME>` — the implementation now matches exactly. - `--format` on `project delete` correctly loses its `-f` short alias (the spec does not define `--format/-f` on this command). - No other commands are affected: `create`, `list`, `show`, `link-resource`, and `unlink-resource` retain `--format/-f` (no conflict since they lack `--force`), and `init` already had `--force/-f` correctly. ### Code Quality ✅ - Changes are minimal and focused: 3 lines in `project.py` (docstring + two `typer.Option` declarations). - Module docstring updated to reflect spec-aligned flag signatures. - Commit message follows Conventional Changelog format with proper `ISSUES CLOSED: #911` footer. ### Test Quality ✅ - New BDD scenario "delete command accepts -f short form for --force" is **meaningful**: it creates a project with linked resources (which would fail without `--force`), then invokes delete with `-f`, proving `-f` maps to `--force`. - The step definition correctly uses `CliRunner` (not direct Python function call) to exercise Typer's actual argument parser — this is the right approach for testing CLI flag binding. - Proper try/finally cleanup of monkey-patches. ### Quality Gates Previous reviewer confirmed all gates pass: - `nox -e lint`: PASSED - `nox -e typecheck`: PASSED (0 errors, 0 warnings) - `nox -e unit_tests`: PASSED (38 scenarios, 0 failed) ### Minor Observations (non-blocking) - `project.py` exceeds the 500-line guideline, but this is a pre-existing condition not introduced by this PR. - The `# type: ignore[import-untyped]` on behave import in the step file is pre-existing, not introduced here. No issues found. Proceeding with merge.

freemo referenced this pull request 2026-04-02 08:21:45 +00:00

fix(cli): resolve --force/-f short form conflict on project delete #911

freemo commented 2026-04-02 16:54:58 +00:00

Author

Owner

Copy link

Review claimed by reviewer pool instance reviewer-pool-1. Dispatching independent code review.

Review claimed by reviewer pool instance reviewer-pool-1. Dispatching independent code review.

freemo reviewed 2026-04-02 16:59:37 +00:00

freemo left a comment

Copy link

Independent Code Review — APPROVED ✅

Summary

Reviewed the complete diff (3 files, 1 commit) against the specification and project conventions. This is a clean, well-scoped bug fix that correctly resolves the -f short flag conflict on project delete.

Specification Alignment ✅

• The spec defines agents project delete [--force|-f] [--yes|-y] <NAME> — the implementation now matches exactly.
• --format on project delete correctly loses its -f short alias (the spec does not define --format/-f on this command).
• No other commands are affected: create, list, show, link-resource, and unlink-resource retain --format/-f (no conflict since they lack --force), and init already had --force/-f correctly.

Code Changes Verified ✅

Three precise changes in project.py:

1. Module docstring updated: [--force] [--yes] → [--force|-f] [--yes|-y]
2. delete command force param: Added -f short alias to typer.Option("--force", "-f", ...)
3. delete command output_format param: Removed -f from typer.Option("--format", ...) (long-form only)

Test Quality ✅

• New BDD scenario "delete command accepts -f short form for --force" is meaningful: it creates a project with linked resources (which would fail without --force), then invokes delete with -f via CliRunner, proving -f maps to --force.
• The step definition correctly uses CliRunner (not direct Python function call) to exercise Typer's actual argument parser — this is the right approach for testing CLI flag binding.
• Proper try/finally cleanup of monkey-patches in the new step.

Commit Quality ✅

• Single atomic commit with Conventional Changelog format: fix(cli): add -f short form to project delete --force
• Proper ISSUES CLOSED: #911 footer.
• Branch name fix/project-delete-force-short-form follows conventions.

PR Metadata ✅

• Type/Task label present
• Milestone v3.4.0 assigned (matches issue)
• Closes #911 in PR body

Minor Observations (non-blocking)

• project.py exceeds the 500-line guideline — pre-existing, not introduced by this PR.
• # type: ignore[import-untyped] on behave import in step file — pre-existing.

No issues found. Proceeding with merge.

## Independent Code Review — APPROVED ✅ ### Summary Reviewed the complete diff (3 files, 1 commit) against the specification and project conventions. This is a clean, well-scoped bug fix that correctly resolves the `-f` short flag conflict on `project delete`. ### Specification Alignment ✅ - The spec defines `agents project delete [--force|-f] [--yes|-y] <NAME>` — the implementation now matches exactly. - `--format` on `project delete` correctly loses its `-f` short alias (the spec does not define `--format/-f` on this command). - No other commands are affected: `create`, `list`, `show`, `link-resource`, and `unlink-resource` retain `--format/-f` (no conflict since they lack `--force`), and `init` already had `--force/-f` correctly. ### Code Changes Verified ✅ Three precise changes in `project.py`: 1. Module docstring updated: `[--force] [--yes]` → `[--force|-f] [--yes|-y]` 2. `delete` command `force` param: Added `-f` short alias to `typer.Option("--force", "-f", ...)` 3. `delete` command `output_format` param: Removed `-f` from `typer.Option("--format", ...)` (long-form only) ### Test Quality ✅ - New BDD scenario "delete command accepts -f short form for --force" is **meaningful**: it creates a project with linked resources (which would fail without `--force`), then invokes delete with `-f` via `CliRunner`, proving `-f` maps to `--force`. - The step definition correctly uses `CliRunner` (not direct Python function call) to exercise Typer's actual argument parser — this is the right approach for testing CLI flag binding. - Proper `try/finally` cleanup of monkey-patches in the new step. ### Commit Quality ✅ - Single atomic commit with Conventional Changelog format: `fix(cli): add -f short form to project delete --force` - Proper `ISSUES CLOSED: #911` footer. - Branch name `fix/project-delete-force-short-form` follows conventions. ### PR Metadata ✅ - `Type/Task` label present - Milestone v3.4.0 assigned (matches issue) - `Closes #911` in PR body ### Minor Observations (non-blocking) - `project.py` exceeds the 500-line guideline — pre-existing, not introduced by this PR. - `# type: ignore[import-untyped]` on behave import in step file — pre-existing. No issues found. Proceeding with merge.

freemo merged commit c63f397b6c into master 2026-04-02 16:59:48 +00:00

freemo referenced this pull request from a commit 2026-04-02 16:59:50 +00:00

fix(cli): add -f short form to project delete --force (#1263)

freemo deleted branch fix/project-delete-force-short-form 2026-04-02 16:59:50 +00:00

freemo referenced this pull request 2026-04-02 16:59:56 +00:00

fix(cli): resolve --force/-f short form conflict on project delete #911

freemo referenced this pull request 2026-04-02 17:11:30 +00:00

[Automated] Product Build Session State #1314

freemo referenced this pull request 2026-04-02 17:20:01 +00:00

[Automated] Product Build Session State #1314

freemo referenced this pull request 2026-04-02 17:34:51 +00:00

[Automated] Product Build Session State #1393

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

auto/needs-reevaluation

Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  

controller-managed

Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  

auto/blocked-by-deps

PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  

auto/ci-timeout

Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  

auto/claimed-implementer

Currently being processed by an implementer worker.

  

auto/claimed-merge

Currently being processed by the merge driver.

  

auto/claimed-reviewer

Currently being processed by a reviewer worker.

  

auto/driver-down

Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  

auto/invariant-violation

Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  

auto/last-attempt-tier-0

In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-1

In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-2

In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  

auto/last-attempt-tier-min

In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  

Automation Tracking

Tracking issues used by the AI Automation system for agents to communicate and report.

  

auto/needs-conflict-resolution

Rebase conflict needs LLM conflict-resolver.

  

auto/needs-implementer

Failing CI needs implementer attention.

  

auto/postmortem

Documenting a driver incident or rollback.

  

auto/ready-to-merge

Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  

auto/restart-throttled

Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  

auto/revert

Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  

auto/sentinel

Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  

auto/stale-inactivity

No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  

auto/unstable

Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  

Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  

Bounty

$100

A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$1000

A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$10000

A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$20

A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$2000

A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$250

A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$50

A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$500

A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$5000

A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$750

A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  

MoSCoW

Could have

Could have feature in order to satisfy the epic/legendary.

  

MoSCoW

Must have

Must have feature in order to satisfy the epic/legendary.

  

MoSCoW

Should have

Should have feature in order to satisfy the epic/legendary.

  

Needs Feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  

Points

1

1 man-hours worth of work for an expert with no learning curve.

  

Points

13

13 man-hours worth of work for an expert with no learning curve.

  

Points

2

2 man-hours worth of work for an expert with no learning curve.

  

Points

21

21 man-hours worth of work for an expert with no learning curve.

  

Points

3

3 man-hours worth of work for an expert with no learning curve.

  

Points

34

34 man-hours worth of work for an expert with no learning curve.

  

Points

5

5 man-hours worth of work for an expert with no learning curve.

  

Points

55

55 man-hours worth of work for an expert with no learning curve.

  

Points

8

8 man-hours worth of work for an expert with no learning curve.

  

Points

88

88 man-hours worth of work for an expert with no learning curve.

  

Priority

Backlog

This ticket has backlogged priority and is not to be worked on yet

  

Priority

CI Blocker

Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  

State

Completed

The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  

State

Duplicate

A ticket that represents the same content as an existing ticket.

  

State

In Progress

A ticket that is actively being developed.

  

State

In Review

A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  

State

Paused

This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  

State

Unverified

All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  

State

Verified

The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  

State

Wont Do

This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  

Type

Automation

Any edits or discussion about the AI automated coding system.

  

Type

Bug

Something that doesnt work as intended.

  

Type

Discussion

Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  

Type

Documentation

An error or improvement needed in the documentation.

  

Type

Epic

Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  

Type

Feature

Some new functionality not present.

  

Type

Legendary

A type of Epic which will contain other Epics.

  

Type

Refactor

A code change that restructures existing code without changing its external behavior.

  

Type

Support

Someone needs help using the project.

  

Type

Task

A generic task that doesnt fit into the other type categories.

  

Type

Testing

Work exclusively focusing on fixing or expanding testing.

No labels

auto/needs-reevaluation

controller-managed

auto/blocked-by-deps

auto/ci-timeout

auto/claimed-implementer

auto/claimed-merge

auto/claimed-reviewer

auto/driver-down

auto/invariant-violation

auto/last-attempt-tier-0

auto/last-attempt-tier-1

auto/last-attempt-tier-2

auto/last-attempt-tier-min

Automation Tracking

auto/needs-conflict-resolution

auto/needs-implementer

auto/postmortem

auto/ready-to-merge

auto/restart-throttled

auto/revert

auto/sentinel

auto/stale-inactivity

auto/unstable

Blocked

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs Feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

CI Blocker

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Automation

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Refactor

Type

Support

Type

Task

Type

Testing

Milestone

Clear milestone

No items

No milestone

v3.4.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

freemo

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.

Blocks

#911 fix(cli): resolve --force/-f short form conflict on project delete

cleveragents/cleveragents-core

Reference

cleveragents/cleveragents-core!1263

No description provided.