teknologi-umum / gitgram Goto Github PK

@TokoBapak is using gitgram (of course) and Github Discussion to talk all things regarding the project. Most people don't get the notification unless mentioned. It didn't appeared on the Telegram channel anyway.

A few actions that most likely will help us:

• discussion_comment.created -> <user> left a comment on <discussion title>
• discussion.created -> <user> started a discussion on <category>: <discussion title>
• discussion.closed -> <user> closed discussion on <category>: <discussion title>
• discussion.answered -> <user> marked <category>: <discussion title> as answered
• discussion.pinned -> <user> pinned a discussion on <category>: <discussion title>
• discussion.reopened -> <user> reopened a discussion on <category>: <discussion title>

Documentations:

• discussion docs: https://docs.github.com/webhooks-and-events/webhooks/webhook-events-and-payloads#discussion
• discussion_comment docs: https://docs.github.com/webhooks-and-events/webhooks/webhook-events-and-payloads#discussion_comment

the changes field, which is used here:

simply add the changes field to the GithubAdapter like any other field here: https://github.com/teknologi-umum/gitgram/blob/master/src/application/adapters/GithubAdapter.ts

After somebody push a commit to master, the CI would run. After that succeeds, a container image should be created.

Should create two variants:

• alpine
• bullseye (or latest Debian)

For each variant, should create multiple tags:

• latest (synonymous with latest-bullseye)
• latest-alpine
• Git SHA commit

Try spamming on GitHub doing some activities that activates the webhook for 15 minutes, and see if you get any notification.

This is a bug that can be fixed by checking the length of the text for each webhook item to be send on Telegram before sending it.

currently it sends the wrong body which results in an empty body, it should send changes.body.from (old) and comments.body (new)

Maybe we'll just focus on Github and Gitlab first, then we can work our way through Gitea and Bitbucket later on.

Github reference: https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads
Gitlab reference: https://docs.gitlab.com/ee/user/project/integrations/webhook_events.html

some reference that parses data from multiple providers: https://github.com/go-playground/webhooks

Initial setup has been done in #26, but it only covers a single function. We need more unit tests.

anunya anu

currently it uses throttle which ignores events that occured too frequent, what we actually want is something like this:

Current Condition

--1-2-3-4-5-6--> // every 500ms

turned into:

--1---3---5----> // every 1s

we lost some events

What We Want

--1-2-3-4-5-6--> // every 500ms

turned into:

--1---2---3----> // every 1s

we no longer losing some events because we buffered past events and then send it based on the configured interval

References

• https://github.com/bkon/rx-op-lossless-throttle
• https://www.g9labs.com/2016/03/21/lossless-rate-limiting-with-rxjs/

Sentry Issue: GITGRAM-1

GrammyError: Call to 'sendMessage' failed! (400: Bad Request: can't parse entities: Unclosed start tag at byte offset 161)
  File "/home/app/dist/src/presentation/TelegramPresenter.js", line 41, in Object.next
    await this._bot.api.sendMessage(info[0].targetId.toString(), message, {

Implement adapter to convert the event payload that Gitlab sends into our interface. See https://github.com/teknologi-umum/gitgram/blob/master/src/application/adapters/GithubAdapter.ts for reference