-
Notifications
You must be signed in to change notification settings - Fork 74
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
Migrate to sbt-typelevel
in series/1.x
#603
Migrate to sbt-typelevel
in series/1.x
#603
Conversation
13040ef
to
7d58e9c
Compare
@@ -6,6 +6,8 @@ ThisBuild / tlBaseVersion := "1.5" | |||
ThisBuild / crossScalaVersions := Seq(Scala213, Scala212, Scala3) | |||
ThisBuild / scalaVersion := Scala213 | |||
ThisBuild / startYear := Some(2018) | |||
ThisBuild / tlSitePublishBranch := None |
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.
ThisBuild / tlSitePublishBranch := None |
If you publish the site for 1.x tags, then it will override the 2.x site. Either we should set up versioned documentation, or you should never publish the site from the 1.x branch/tags ever. WDYT?
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.
Eh, you're probably right. I think sbt-typelevel should have some explicit settings to disable publishing site. It could be odd from some angle but it makes sense in the case of the multibranch project without a versioned site. I think it's worth discussing it in the sbt-typelevel space.
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.
@armanbilge I've started typelevel/sbt-typelevel#137, so would be lovely to get your thoughts on it.
This is a backport of #592.