[bug]: plane-compose PyPI metadata and CLI error footer point at github.com/makeplane/compose, which does not exist
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Describe the bug
The plane-compose package on PyPI advertises a source repository and bug tracker that do not exist. From https://pypi.org/pypi/plane-compose/json:
"project_urls": {
"Bug Tracker": "https://github.com/makeplane/compose/issues",
"Documentation": "https://github.com/makeplane/compose/tree/main/docs",
"Homepage": "https://github.com/makeplane/compose",
"Repository": "https://github.com/makeplane/compose",
"Source Code": "https://github.com/makeplane/compose"
}
https://github.com/makeplane/compose returns 404, and compose does not appear in the makeplane org's public repo listing.
This is not just a metadata nit: the CLI prints that URL on every unhandled error, as the place to report the problem —
If this error persists, please report it at:
https://github.com/makeplane/compose/issues
— so anyone hitting a bug is sent to a dead link. It took some digging to work out that plane-compose issues are actually filed here in makeplane/plane (e.g. #9000, #9001, #9002, #9003, #9004, #9558).
Expected behavior
Either make the repo public, or point the metadata and the CLI error footer at https://github.com/makeplane/plane/issues so reports land somewhere real.
Also worth noting the Documentation URL has the same problem — there is no published docs location that resolves.
Environment
- plane-compose 0.5.2 (metadata checked against the live PyPI JSON API)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the plane-compose package metadata and the CLI's unhandled-error footer. Verify the current PyPI project URLs and the URL printed on errors; done means they point to a resolving Plane repository or issue tracker, with the documentation link addressed as well.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100