-
Notifications
You must be signed in to change notification settings - Fork 155
Publish tweaks + documentation #1107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
df721c4 to
7973294
Compare
7973294 to
ef84634
Compare
84e873f to
d99e922
Compare
When setting up publishing from CI, version / computeVersion is the only missing parameter to publish locally. This allows to have "publish local" work after that setup.
--secret-key and --secret-key-password, so that users can specify things like ``` --secret-key config:pgp.secret-key --secret-key-password config:pgp.secret-key-password ```
d99e922 to
314aeb3
Compare
romanowski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have comments mostly related to docs.
lwronski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes in code LGTM.
223cdf4 to
20422b6
Compare
Those that are meant to be customized on CIs
Rather than a Scala 2.13 + a Scala 3 one
20422b6 to
cf3c728
Compare
|
|
||
| To override this default value, set the `publish.computeVersion` directive, like | ||
| ```scala | ||
| //> using publish.computeVersion "git:tag" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should link here to a doc explaining what computeVersions are supported and how each work
| provided as a convenience. | ||
|
|
||
| <!-- TODO Automatically generate that? --> | ||
| | | `using` directive | Command-line option | Example values | Notes | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we shouldn't explain what options means, since Licences is self-descriptive but VSC may not be
romanowski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have left some comments but they can be applied in the follow-up.
|
|
||
| ### Other pre-defined repositories | ||
|
|
||
| All pre-defined repositories accepted by coursier, such as `jitpack` or `sonatype:snapshots`, are accepted as repositories for publishing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does Coursier have a piece of doc about these repositories? If so, can we link it?
This tweaks things in the
publishsub-command (allowing to list licenses or checksum types, better defaults, acceptgithubas repository, …), and adds documentation for it.