-
Notifications
You must be signed in to change notification settings - Fork 18k
x/build/cmd/releasebot: does not build on HEAD #24598
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
Comments
GitHub changed there API from using int to int64, and breaks everything that uses that API. This is found by smallrepo.com, at https://smallrepo.com/builds/20180329-172031-7b4b496e |
Change https://golang.org/cl/103475 mentions this issue: |
I have a fix. The |
Change https://golang.org/cl/103398 mentions this issue: |
When editing a comment, the current code used the issue number in place of the comment ID. But the EditComment endpoint needs the comment ID. The issue number is not needed at all in updateGithubComment because the EditComment endpoint uses the repository and comment ID to uniquely identify the comment. References: - https://developer.github.com/v3/issues/comments/#edit-a-comment. - https://godoc.org/github.com/google/go-github/github#IssuesService.EditComment. Updates golang/go#24598. Updates google/go-github#883. Updates google/go-github#597. Change-Id: Iae9d967d7be7a75b1bcee7118a3c80fe8f2375b4 Reviewed-on: https://go-review.googlesource.com/103398 Reviewed-by: Brad Fitzpatrick <[email protected]>
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go 1.10
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?Does not matter.
What did you do?
go get -u golang.org/x/build/cmd/releasebot
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
Build succeeds
What did you see instead?
Build fails
The text was updated successfully, but these errors were encountered: