From: Ammar Faizi <[email protected]>
To: Muhammad Rizki <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: Re: [RFC PATCH v5 00/18] Refactor Telegram & initial work Discord
Date: Mon, 26 Sep 2022 04:58:30 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 26 Sep 2022 04:52:53 +0700, Muhammad Rizki wrote:
> On 26/09/2022 04.48, Ammar Faizi wrote:
>> On 9/26/22 4:37 AM, Muhammad Rizki wrote:
>>> On 26/09/2022 04.31, Ammar Faizi wrote:
>>>> On 9/26/22 4:14 AM, Muhammad Rizki wrote:
>>>>> Make initial work for Discord bot, it's still undone but it can run.
>>>>
>>>> OK, I run it. The bot now responds the $sync command. But how to use it
>>>> exactly? I don't find a command list or usage manual of the bot.
>>>>
>>>
>>> As the title said, this PATCH should only be for refactoring the
>>> Telegram bot and initializing the Discord bot work. If you want more
>>> commands, I will add them to the new PATCH. My plan created this RFC was
>>> only to ask for the commit style is okay or not.
>>
>> OK.
>>
>> This series looks good to me now. Can't wait to see the completion and
>> incremental patches for it later. I start loving the way you split the
>> changes into smaller-manageable-reviewable pieces like this.
>>
>
> Ah, thanks for the compliment. Do you want to apply this to the master
> branch, or do you want to wait for the new PATCH with the complete version?
I think this has been stalled for too long, I'll take it.
Applied, thanks!
[01/18] telegram: Move the Telegram bot source code
commit: 542fae7e49e800ddf8ac92ae04d5200a85778d31
[02/18] telegram: Refactor the Telegram bot database method
commit: 07be1617820719c765496d9118aeab127bb4c0bd
[03/18] telegram: Rename some functions in scraper/bot.py
commit: c84a62f2cfd11386dbe8d3a7e453ec8c8ef801b9
[04/18] Add ignore file for .env
commit: befcb317ce18657846592b66b9586dda1f51c280
[05/18] telegram: Refactor the Telegram bot
commit: c8e00eca92c1f91779776e5209546f8057a3b6b1
[06/18] telegram: Renames in telegram mailer directory
commit: 46a18b84cae66ab0f387e8b5ed6f1991d2f2ca6f
[07/18] Move scraper and utility file
commit: e6c42e102ee3dd48f9d265d01b8e486d7504c878
[08/18] discord: Initial work for the Discord bot
commit: 6819180f8b73b0ba60a5f5d6b22b146d80685fc4
[09/18] discord: Add success run notice on_ready event
commit: c5c4da9f2af2ed94bfc91fe18ed64e34fa283d39
[10/18] discord: Add error handler on events
commit: bb13e25c09e65385ce6a9319518ddd794e95c566
[11/18] Move db.sql to combine the database with Discord and Telegram
commit: 9c014880785cc48e7bccb62549ff5610993e32bd
[12/18] discord: Add database tables for the Discord bot
commit: 747963497077be01719b41591ba323451e902daa
[13/18] discord: Add initial Discord bot database instance
commit: b5ceeab16ac78b3db47bf9bf544064c0b488dd22
[14/18] discord: Add save_atom() in database insertion
commit: e6ec8ad6e9853de6b2d83fe06e485e294a2e289c
[15/18] discord: Add save_broadcast() in database insertion
commit: 6d09ec1babac2f444fb29b21d38ef2b875a3c189
[16/18] discord: Add save_discord_mail() in database insertion
commit: 3ffbcd3b77ee62575b3bf002987bb5a84bf6286e
[17/18] discord: Add save_email() in database insertion
commit: 62473c85394e1eeb3e86f2ef2073df1047693d09
[18/18] discord: Add $sync basic command
commit: 949ca804c527978b070e89c0389d172a53aedfa5
Best regards,
--
Ammar Faizi
next prev parent reply other threads:[~2022-09-25 21:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 21:14 [RFC PATCH v5 00/18] Refactor Telegram & initial work Discord Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 01/18] telegram: Move the Telegram bot source code Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 02/18] telegram: Refactor the Telegram bot database method Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 03/18] telegram: Rename some functions in scraper/bot.py Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 04/18] Add ignore file for .env Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 05/18] telegram: Refactor the Telegram bot Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 06/18] telegram: Renames in telegram mailer directory Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 07/18] Move scraper and utility file Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 08/18] discord: Initial work for the Discord bot Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 09/18] discord: Add success run notice on_ready event Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 10/18] discord: Add error handler on events Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 11/18] Move db.sql to combine the database with Discord and Telegram Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 12/18] discord: Add database tables for the Discord bot Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 13/18] discord: Add initial Discord bot database instance Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 14/18] discord: Add save_atom() in database insertion Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 15/18] discord: Add save_broadcast() " Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 16/18] discord: Add save_discord_mail() " Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 17/18] discord: Add save_email() " Muhammad Rizki
2022-09-25 21:14 ` [RFC PATCH v5 18/18] discord: Add $sync basic command Muhammad Rizki
2022-09-25 21:31 ` [RFC PATCH v5 00/18] Refactor Telegram & initial work Discord Ammar Faizi
2022-09-25 21:37 ` Muhammad Rizki
2022-09-25 21:48 ` Ammar Faizi
2022-09-25 21:52 ` Muhammad Rizki
2022-09-25 21:58 ` Ammar Faizi [this message]
2022-09-30 12:21 ` Ammar Faizi
2022-09-30 13:39 ` Muhammad Rizki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox