Skip to content

Require unshallow clone to publish in SBT#3070

Merged
jackkoenig merged 1 commit intomainfrom
require-unshallow-to-publish
Mar 4, 2023
Merged

Require unshallow clone to publish in SBT#3070
jackkoenig merged 1 commit intomainfrom
require-unshallow-to-publish

Conversation

@jackkoenig
Copy link
Contributor

Now if you try to publish from a shallow clone, it will error. This check would've helped detect #3069.

</licenses>,
sonatypeCredentialHost := "s01.oss.sonatype.org",
sonatypeRepository := "https://s01.oss.sonatype.org/service/local",
publish / skip := {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems a little weird to use skip as a hook to error. You may want to add a comment indicating that this is what is going on here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh yeah I meant to add a comment and totally forgot. Yeah there isn't like a "publishing hook" key so I arbitrarily picked this, definitely needs to be explained.

@jackkoenig jackkoenig force-pushed the require-unshallow-to-publish branch from add508d to e92e35f Compare March 4, 2023 19:19
@jackkoenig jackkoenig enabled auto-merge (squash) March 4, 2023 19:30
@jackkoenig jackkoenig merged commit 73cdddb into main Mar 4, 2023
@jackkoenig jackkoenig deleted the require-unshallow-to-publish branch March 4, 2023 19:58
@jackkoenig jackkoenig added the Internal Internal change, does not affect users, will be included in release notes label Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Internal Internal change, does not affect users, will be included in release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants