makeplane / makeplane/plane

[bug]: plane import and plane apply documented but not implemented in plane-compose 0.2.0

Open
#9,000 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Context for this and four related tickets: https://github.com/orgs/makeplane/discussions/8999

I have searched existing issues; no existing report covers this. Filing via API rather than the issue form, so the form fields (Environment, Browser, Variant, Version) are inlined below.

  • Environment: Production
  • Browser: Other (CLI tool)
  • Variant: Cloud (tested against api.plane.so)
  • Version: plane-compose 0.2.0 (note: plane --version self-reports 0.1.0 -- separate ticket forthcoming)
Current behavior

Two commands are referenced in user-facing materials shipped with plane-compose 0.2.0 but are absent from the actual CLI:

  • plane import -- the auto-generated work/inbox.yaml from plane clone contains the comment line: # Use 'plane import' to bring specific items into this file. Running plane import returns Error: No such command 'import'.
  • plane apply -- the PyPI README for plane-compose 0.2.0 lists plane apply and plane apply --dry-run under "Work Items (Declarative)" as the "Declarative sync with delete support" path. Running plane apply returns Error: No such command 'apply'.

These are the documented paths for two important workflows: taking ownership of cloned items so they can be edited and pushed back (import), and declarative sync with deletion support (apply). Without them, there is no working path for the workflows they describe.

What I expect: either ship the commands, or remove the references from inbox.yaml and the PyPI README so users don't lose time looking for them.

Steps to reproduce
  1. pipx install plane-compose (installs 0.2.0).
  2. plane auth login against any workspace.
  3. plane clone <uuid> --workspace <slug> for any project.
  4. cat work/inbox.yaml -- observe the comment referencing plane import.
  5. Run plane import:
    $ plane import
    Usage: plane [OPTIONS] COMMAND [ARGS]...
    Try 'plane --help' for help.
    Error: No such command 'import'.
    
  6. Run plane apply:
    $ plane apply
    Usage: plane [OPTIONS] COMMAND [ARGS]...
    Try 'plane --help' for help.
    Error: No such command 'apply'.
    
  7. Confirm the PyPI reference at https://pypi.org/project/plane-compose/ -- the "Work Items (Declarative)" section lists both commands.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the installed plane CLI command list and the generated work/inbox.yaml reference, then compare them with the PyPI README's Work Items (Declarative) section. Determine whether the documented import and apply workflows are intended to be shipped or removed. Done means the CLI and its user-facing references agree, with the reported commands either working or no longer advertised.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, documentation
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.