Repository navigation
Announce nightly builds and attach APKs in Telegram comments - #777
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Published Android nightlies now post a comment beneath a configured Telegram announcement using the same wording and links as Discord, then attach the exact signed APK as a reply. The full announcement stays in a text message because document captions have a shorter limit.
The runner builds and caches a pinned official Telegram Bot API executable for local uploads up to 2 GB. It binds the server to loopback, uses a disposable session and logs out/stops the owned server on completion or cancellation. The additional API ID/hash are read from environment secrets; group/message IDs accept variables or secrets. Delivery is not retried automatically.
Updates the existing root nightly documentation with Telegram delivery behavior. The scheduled workflow remains on master and continues building develop; notification helpers are checked out separately from the workflow commit, so branch alignment is unnecessary.
Validation
--helpon Ubuntu 24.04 ARM64 using the notification build script.