Since both sbt-site and sbt-git are now AutoPlugins, it makes sense to go the same route and have inclusion of settings (and dependent settings) managed via the enablePlugins mechanism.
This changes SbtGhPages to GhPagesPlugin to match with the changes undergone in other plugins already during their migration to AutoPlugin (eg SbtSite => SitePlugin, SbtGit => GitPlugin etc.).
Users can use the plugin and include settings by simply adding an enablePlugins(SbtGhPages) statement to their build.sbt file.
Since both sbt-site and sbt-git are now
AutoPlugin
s, it makes sense to go the same route and have inclusion of settings (and dependent settings) managed via theenablePlugins
mechanism.This changes
SbtGhPages
toGhPagesPlugin
to match with the changes undergone in other plugins already during their migration to AutoPlugin (eg SbtSite => SitePlugin, SbtGit => GitPlugin etc.).Users can use the plugin and include settings by simply adding an
enablePlugins(SbtGhPages)
statement to their build.sbt file.