Skip to content
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

Commits per build inquiry #269

Open
ChristopherDavenport opened this issue Jun 24, 2018 · 1 comment
Open

Commits per build inquiry #269

ChristopherDavenport opened this issue Jun 24, 2018 · 1 comment

Comments

@ChristopherDavenport
Copy link
Contributor

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.

@juanpedromoreno
Copy link
Member

@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:

  1. Delete current files.
  2. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants