purescript / purescript/registry
support for polyrepos
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 54
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
I would like to spago publish v4.6.0 of https://github.com/rowtype-yoga/purescript-protobuf
Result:
✘ The manifest file specifies a location (
{"githubOwner":"rowtype-yoga","githubRepo":"purescript-protobuf","subdir":"library"}
) that differs from the location in the registry metadata (
{"githubOwner":"rowtype-yoga","githubRepo":"purescript-protobuf"}
). If you would like to change the location of your package you should
submit a transfer operation.
This is true, I have changed the location of the package. But I cannot submit a transfer operation because I have never published this package with myself in the package.publish.owners field. Advice please?
Contributor guide
No contributing guide indexed for this repository
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 reproducing the spago publish v4.6.0 result for purescript-protobuf and read the registry README section on “Transfer a package.” Trace how the manifest location with subdir: "library" is compared with registry metadata, then define and test the supported path for publishing a package whose location changed.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100