Fix UnauthorizedError on GitHub Enterprise publish

[necosta]

When gitHostingURL is set, we see the following error:

Error making request to GitHub
 | => bat microsites.github.GitHubOps.$anonfun$run$1(GitHubOps.scala:208)
	at uncancelable @ org.http4s.client.ConnectionManager$.pool(ConnectionManager.scala:83)
	at uncancelable @ org.http4s.client.ConnectionManager$.pool(ConnectionManager.scala:83)
	at flatMap @ org.http4s.client.PoolManager.releaseRecyclable(PoolManager.scala:225)
	at uncancelable @ org.http4s.client.ConnectionManager$.pool(ConnectionManager.scala:83)
	at unsafeRunSync @ microsites.MicrositeAutoImportSettings.$anonfun$micrositeTasksSettings$14(MicrositeKeys.scala:496)
	at withPermit @ org.http4s.client.PoolManager.shutdown(PoolManager.scala:370)
	at uncancelable @ org.http4s.client.ConnectionManager$.pool(ConnectionManager.scala:83)
	at withPermit @ org.http4s.client.PoolManager.shutdown(PoolManager.scala:370)
	at guarantee$extension @ org.http4s.client.blaze.Http1Connection.$anonfun$executeRequest$2(Http1Connection.scala:193)
	at map @ fs2.internal.CompileScope.$anonfun$close$9(CompileScope.scala:246)
Caused by: UnauthorizedError(Bad credentials, https://docs.github.com/rest)

We need to adjust GithubConfig base/authorize/accessToken URLs to contain the gitHostingURL host.

---

@TomyMeren , can you:

1. Clone my repo (branch fix/github_enterprise)
2. Run publishLocal (haven't checked but should be configured)
3. On your repo, change resolver to include resolvers += Resolver.mavenLocal, adjust github4s version to this published version
4. Compile, run and inform if it's now working

---

[fedefernandez]

Thanks @necosta. Please, @TomyMeren, let me know if this fixes the issue.

[necosta]

After reading google/go-github#958, adjusted baseUrl logic.

[necosta]

Added edge-case scenario for when micrositeGitHostingUrl is still pointing to public GitHub:

case Right(url) if url.getHost == "github.com" => GithubConfig.default

[TomyMeren]

Good progress! @necosta.

The current error is this: NotFoundError(Not Found, https://docs.github.com/enterprise/3.4/rest)
After Debugging I've seem that it is throwing here

sbt-microsites/src/main/scala/microsites/github/GitHubOps.scala

Line 200 in 26a426e

gh.gitData.getReference(owner, repo, s"heads/$branch", pagination = None, headers = headers)

It could be a problem with the method updateReference in the github4s repo but I could't find the https://docs.github.com/enterprise/3.4/rest value in the project

[TomyMeren]

LGTM!

[necosta]

Thanks @TomyMeren for testing. I did mess up the PR when I last updated, will get the changes from the "patched" branch, adjust the tests, then I think we are good to merge. Will do it now.

[TomyMeren]

When I publish the sbt-microsite project locally, for use in the project, version 1.4.1+1.....-SNAPSHOT is created. The latest release version is 1.4.2. Do you know why this is?

[necosta]

When I publish the sbt-microsite project locally, for use in the project, version 1.4.1+1.....-SNAPSHOT is created. The latest release version is 1.4.2. Do you know why this is?

Yes, publishLocal is configured to build a "SNAPSHOT" version and not a "release" version. It should work this way to avoid any version conflict.

[necosta]

Green CI. It's ready for a final review @fedefernandez , feel free to merge after you approve the PR. Thank you @TomyMeren for testing it.

[TomyMeren]

When I publish the sbt-microsite project locally, for use in the project, version 1.4.1+1.....-SNAPSHOT is created. The latest release version is 1.4.2. Do you know why this is?

Yes, publishLocal is configured to build a "SNAPSHOT" version and not a "release" version. It should work this way to avoid any version conflict.

Sorry for my unclear comment.
I was talking about the difference between 1.4.1 and 1.4.2

[necosta]

When I publish the sbt-microsite project locally, for use in the project, version 1.4.1+1.....-SNAPSHOT is created. The latest release version is 1.4.2. Do you know why this is?

Yes, publishLocal is configured to build a "SNAPSHOT" version and not a "release" version. It should work this way to avoid any version conflict.

Sorry for my unclear comment. I was talking about the difference between 1.4.1 and 1.4.2

Ah I see. I tried now, I do get 1.4.2-SNAPSHOT when publishing locally. Perhaps you are missing the git tag?

[TomyMeren]

Yes It was a missing tag
LGTM!

[necosta]

Green CI and all comments resolved. Is it ok to merge to master @fedefernandez ? thanks