Repository navigation
feat(github-bridge): send GitHub events as Telegram posts - #58
Merged
Merged
Conversation
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
1 participant
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.
Second step of #56: GitHub pushes on Telegram get a short caption, hashtags and a button, and long bodies stop filling the card.
Postwith the hashtags#issue,#commentor#pushplus the repository, one line such as "m1ngsama 关闭了 Production bot has been silent since early May #22", and a button (打开 Production bot has been silent since early May #22, 查看评论, 查看改动).…. Production bot has been silent since early May #22 renders at 1000×400 instead of 1000×1200.Broadcast.SendAsyncnow takes the messages directly.