Commit issue via plugin when WikiGDrive Is not synchronized

[monpie3]

If a file is added directly to the repository and WikiGDrive is not synchronized, committing via the plugin stops working.

Expected Behavior:
Committing via the plugin should work try to synchronize WikiGDrive or display an appropriate error message with suggested corrective actions.

Steps to Reproduce:

1. Add a file directly to the repository.
2. Do not synchronize WikiGDrive.
3. Attempt to commit using the plugin or try to commit and push in directly in wikigdrive (don't pull before it).
4. Observe the error

[monpie3]

I fixed it by synchronizing WikiGDrive, but I think it would be better if it happened automatically when trying to commit. To discuss in the meeting.

[pierzchala-m]

Example:

The change b52cf50 was introduced via a PR, so the local Git repository used by WikiGDrive did not have this commit yet. When attempting to commit new edits through the plugin (without pulling first - this option isn't available from the plugin), the operation failed because the local branch was behind the remote.

When attempting to commit new edits through the plugin before pulling those changes, the operation failed because the local repository was out of sync with the remote.

Current fix:

Reset and Pull

Expected improvement:

When detecting such a mismatch (e.g., remote commits not yet pulled), WikiGDrive could:

• Automatically perform a pull or background sync before committing, or
• Display a clear message like “Your WikiGDrive repository is out of sync with remote changes. Please synchronize before committing.” with an option to trigger sync directly.

This would prevent failed commits caused by missing sync and improve user experience, especially when multiple contributors add files directly on GitHub.