fix: change keyring to use persistent secret service on linux

Author: JayanAXHF

Cargo.lock

@@ -13,11 +13,11 @@ keywords = ["tui", "cli", "github", "prodcutivity", "ratatui"]
 categories = ["command-line-utilities", "command-line-interface"]
 
 [workspace]
-members = [
-	"crates/hyperrat"
-,
-	"crates/ratatui-toaster"
-]
+members = ["crates/hyperrat", "crates/ratatui-toaster"]
+
+[features]
+default = ["keyring/linux-native"]
+persist-token = ["keyring/sync-secret-service"]
 
 [dependencies]
 anyhow = "1.0"
@@ -30,7 +30,7 @@ edit = "0.1.5"
 futures = "0.3.31"
 hyperrat = { path = "crates/hyperrat", version = "0.1.1" }
 inquire = "0.9.3"
-keyring = { version = "3.6.3", features = ["apple-native", "windows-native", "linux-native"] }
+keyring = { version = "3.6.3", features = ["apple-native", "windows-native"] }
 octocrab = "0.49.5"
 pulldown-cmark = "0.13.0"
 regex = "1.11.1"

Cargo.toml

@@ -99,6 +99,9 @@ See [KEYBINDINGS.md](./KEYBINDS.md) for a list of keybindings used in the applic
 
 ### Token Security
 
+> [!NOTE]
+> To persist the token across reboots (i.e. to store it on disk) on Linux, build with the `persist-token` feature flag. This requires for `dbus` to be present and `DBUS_SESSION_BUS_ADDRESS` to be set.
+
 `gitv` uses the `keyring` crate to securely store your GitHub token in your system's credential store. This means that your token is encrypted and protected by your operating system's security features, providing a secure way to manage your authentication credentials.
 
 ### Contributing