From 9ec740b0c73e33485e1d754759de46aa99444733 Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Fri, 6 Nov 2026 10:13:20 +0100 Subject: feat(app): optionally push after each change Changes made in the app could sit unpushed and collide with a later desktop change. The new setting, off by default, pushes after a save, move, rename or delete. It pushes rather than syncs because a rejected push changes nothing, while a pull can stop in a rebase. A failed push only shows a snackbar: the commit stays local and promptOnErrorHandler would delete saved credentials over a missing network. Autofill saves are left out: AutofillSaveActivity closes right after saving, which would cancel the push. TODO.md tracks that. Co-Authored-By: Claude Opus 5.5 --- app/src/main/res/values/strings.xml | 3 +++ 1 file changed, 3 insertions(+) (limited to 'app/src/main/res/values/strings.xml') diff --git a/app/src/main/res/values/strings.xml b/app/src/main/res/values/strings.xml index c8782fad..fa9fb0f3 100644 --- a/app/src/main/res/values/strings.xml +++ b/app/src/main/res/values/strings.xml @@ -126,6 +126,9 @@ Rebase on pull When pulling or syncing, create a merge commit with upstream changes When pulling or syncing, rebase commits that are not present in the remote repository + Push after each change + Push to the remote repository after saving, moving or deleting in the app + Saved on this device, but not pushed. Sync to try again Disable pull to sync action Prevent pulling down on the password list from triggering a Git sync Import PGP key -- cgit v1.2.3