feat: support telegram threads. refactor bot files. (#41)

* feat: support telegram threads. refactor bot files.

keep old codes as commented out for a while.

* chore: update readme

Cargo.toml

@@ -7,17 +7,17 @@ edition = "2021"
 
 [dependencies]
 teloxide = { version = "0.12.2", features = ["macros"] }
-log = "0.4"
+log = "0.4.21"
 pretty_env_logger = "0.5.0"
-tokio = { version =  "1.8", features = ["rt-multi-thread", "macros"] }
-actix-web = "4"
+tokio = { version =  "1.37", features = ["rt-multi-thread", "macros"] }
+actix-web = "4.5.1"
 serde = { version = "1.0", features = ["derive"] }
 dotenv = "0.15.0"
-diesel = { version = "2.0.0", features = ["postgres", "r2d2"] }
+diesel = { version = "2.1.5", features = ["postgres", "r2d2"] }
 rand = "0.8.5"
-reqwest = { version = "0.11.13", features = ["json", "blocking"] }
-reqwest-oauth1 = "0.2.3"
+reqwest = { version = "0.12.3", features = ["json", "blocking"] }
+reqwest-oauth1 = "0.2.4"
 oauth = { version = "0.6", package = "oauth1-request" }
-ureq = { version="2.5.0", features = ["json"] }
-url = "2.3.1"
-diesel_migrations = "2.0.0"
+ureq = { version="2.9.6", features = ["json"] }
+url = "2.5.0"
+diesel_migrations = "2.1.0"

README.md

@@ -66,7 +66,10 @@ If you want to host the bot on your private server.
 
 ## Notes
 
-Gitlab sends a job event for each PR event. So, to avoid duplicate notifications, we use job events instead of PR events. If you want to test PR events, you should select Job event and click test on Gitlab.
+Gitlab sends a job event for each PR event. So, to avoid duplicate notifications, we use job events instead of PR events. If you want to test PR events, you should select Job event and click test on Gitlab
+
+**Telegram threads (topics) are now supported:**
+After adding the bot to the group, simply execute the /start command in the thread where you want to receive notifications.
 
 ## Ways to help
 

migrations/2024-04-11-200504_add_thread_id_column_to_chats/down.sql

@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+ALTER TABLE chats DROP COLUMN thread_id;

migrations/2024-04-11-200504_add_thread_id_column_to_chats/up.sql

@@ -0,0 +1,2 @@
+-- Your SQL goes here
+ALTER TABLE chats ADD COLUMN thread_id VARCHAR(255);