You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have adopted sbt-microsites on linebacker , log4cats as well as many of my other libraries and my Travis CI automation consistently generates 6 commits per build.
I have checks in place that this is only firing against 1 build per merge, and it seems to me excessive to have that numbe of commits for an automated process.
Am I missing something or doing something wrong?
sbt docs/publishMicrosite is the command I am using, based on the documentation.
The text was updated successfully, but these errors were encountered:
@ChristopherDavenport Likely you are using the option Publish using GitHub4s, where we are using the Github API directly with a GH token, by using https://github.com/47deg/github4s. Committing files using the GH API is not intuitive at all, it needs to be done recursively by folder, that’s potentially why you are finding a fixed number of commits, it’d be something like this:
Delete current files.
Commit files for every folder, including the root one.
It could be a little annoying, but as gh-pages is an orphan branch we considered that wasn’t a big deal. The other available option would be Publish the Microsite using ssh keys.
I have adopted sbt-microsites on linebacker , log4cats as well as many of my other libraries and my Travis CI automation consistently generates 6 commits per build.
I have checks in place that this is only firing against 1 build per merge, and it seems to me excessive to have that numbe of commits for an automated process.
Am I missing something or doing something wrong?
sbt docs/publishMicrosite
is the command I am using, based on the documentation.The text was updated successfully, but these errors were encountered: