-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/build/cmd/relui: ability to make minor release announcement tweets via Twitter API #47403
Comments
Change https://golang.org/cl/358899 mentions this issue: |
Change https://golang.org/cl/358897 mentions this issue: |
Change https://golang.org/cl/358898 mentions this issue: |
This CL adds an internal API for making release tweets of various kinds, including the templates used to generate the tweet text and tweet image. It does not have code for using the Twitter API. CL 358898 will do that. For golang/go#40279. For golang/go#47403. Change-Id: Ic0cb2f5f1e59c0fd932aed7c5c4a88decc5a3d8d Reviewed-on: https://go-review.googlesource.com/c/build/+/358897 Run-TryBot: Dmitri Shuralyov <[email protected]> TryBot-Result: Go Bot <[email protected]> Trust: Dmitri Shuralyov <[email protected]> Trust: Alexander Rakoczy <[email protected]> Reviewed-by: Alexander Rakoczy <[email protected]> Reviewed-by: Carlos Amedee <[email protected]>
This allows exercising (and benefiting from improvements offered by) the programmatic tweet creation tasks as soon as the next minor release. The same task will be added and used by relui when possible. For golang/go#40279. Updates golang/go#47403. Change-Id: I8b47f86489e753bea6a767990ff98dd525e668df Reviewed-on: https://go-review.googlesource.com/c/build/+/358899 Run-TryBot: Dmitri Shuralyov <[email protected]> TryBot-Result: Go Bot <[email protected]> Trust: Dmitri Shuralyov <[email protected]> Trust: Alexander Rakoczy <[email protected]> Reviewed-by: Alexander Rakoczy <[email protected]>
Change https://go.dev/cl/388834 mentions this issue: |
Change https://go.dev/cl/388835 mentions this issue: |
Change https://go.dev/cl/393018 mentions this issue: |
There was accidentally one too many "go" in the tweet text for the major Go release type. Updates golang/go#47403. Updates golang/go#40279. Change-Id: I7983bdb78f22c258121348a6cfaa2ed66592db54 Reviewed-on: https://go-review.googlesource.com/c/build/+/393018 Trust: Dmitri Shuralyov <[email protected]> Run-TryBot: Dmitri Shuralyov <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Heschi Kreinick <[email protected]>
When working on CL 358897, I forgot that there's already an SFNT font parser and glyph rasterizer available in the x/image module. Using it produces an equivalent final image, and allows x/build to depend on 1 less module. Also add a regression test for drawTerminal. Updates golang/go#47403. Change-Id: I77166a2180a7db9c81a30f77b12bb20dcd21bd8b Reviewed-on: https://go-review.googlesource.com/c/build/+/388834 Trust: Dmitri Shuralyov <[email protected]> Run-TryBot: Dmitri Shuralyov <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Heschi Kreinick <[email protected]>
Its v1.0.1 version has been recently retracted in esimov/stackblur-go#5. Update to the latest stable version. As a benefit, its new API makes it possible to drop the type assertion. Updates golang/go#47403. Change-Id: I08abac0e19ee32b83441e56ff42d1edc5fac441f Reviewed-on: https://go-review.googlesource.com/c/build/+/388835 Trust: Dmitri Shuralyov <[email protected]> Run-TryBot: Dmitri Shuralyov <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Heschi Kreinick <[email protected]>
During the minor release process, towards the end, an announcement tweet is posted. For example, https://twitter.com/golang/status/1414721238224838666. (The tweet text and image are generated via a template.)
This task is to write Go code that uses the Twitter API to create a tweet with the following inputs:
It can be integrated into relui as part of #47402.
The text was updated successfully, but these errors were encountered: