-
Notifications
You must be signed in to change notification settings - Fork 148
Open
Labels
bugSomething isn't workingSomething isn't workingdocumentationImprovements or additions to documentationImprovements or additions to documentationexperimentalTickets tied to experimental features.Tickets tied to experimental features.publish command
Description
Version(s)
1.5.4
Describe the bug
Docs don't seem to specify how the //> using publish.vcs
directive should be set up for non-GitHub repositories.
https://scala-cli.virtuslab.org/docs/commands/publishing/publish#other-settings
What's there (the url|connection|developer-connection
format) seems quite vague.
We need examples, better errors, or some different behaviour.
To Reproduce
//> using publish.vcs https://git.qwertyuiop.de/crater2150/copret.git
yields
[error] Malformed vcs "https://git.qwertyuiop.de/crater2150/copret.git", expected url|connection|developer-connection
[error] //> using publish.vcs https://git.qwertyuiop.de/crater2150/copret.git
Expected behaviour
I'd expect the reproduction to either pass, or for documentation to provide examples how to handle non-github repositories.
Extra context
- the error seems to originate at https://github.com/VirtusLab/scala-cli/blob/main/modules/options/src/main/scala/scala/build/options/publish/Vcs.scala#L35-L48
- it seems for non-GitHub repositories, the parser expects all 3 components of the
url|connection|developer-connection
format - originally reported on Discord: https://discord.com/channels/632150470000902164/901153021638082660/1326980016545861745
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingdocumentationImprovements or additions to documentationImprovements or additions to documentationexperimentalTickets tied to experimental features.Tickets tied to experimental features.publish command