Invitation to collab on improving Godot VCS APIs for the benefit of this plugin and more #3

Activity

1. theRTC204 commented on Aug 2, 2026

   

   theRTC204

   on Aug 2, 2026

   Owner

   More actions

   @twaritwaikar thank you for reaching out!

   Is there a location in particular that would be best for me to document the limitations I encounter? Should I just be opening issues in the godotengine/godot-cpp project?

   For the moment, the two key areas that I have identified are largely related to the UI and less the actual EditorVCSInterface itself.

   • The version control settings (Project -> Version Control -> Version Control Settings) UI is controlled entirely by the Editor and not exposed to the VCS interface; as a result VCS providers who have authentication concepts that differ from Git (username/password, SSH) will have a difficult time with a fully native integration. Lore, for example, supports an unauthenticated text based identity, as well as a web-based OIDC authentication workflow, where the Lore client returns an authorization URL that the user opens in a browser to provide their credentials. Supporting this OIDC flow would be ideal!
   • The Commit doc's icon buttons are prescribed for a Git-like workflow, with fixed "Fetch", "Pull", "Push" concepts that don't necessarily map to all VCS providers. Lore, for example, does not support distinct "Fetch" & "Pull" operations. Ideally these icons would be exposed via the interface and only VCS-appropriate buttons would render in the UI.
2. twaritwaikar commented on Aug 6, 2026

   

   twaritwaikar

   on Aug 6, 2026

   Author

   More actions

   Reporting them as a bug in https://github.com/godotengine/godot-git-plugin is probably okay?

   We can discuss pulling more of the VCS integration inside the plugins. I wager if the editor can be made almost fully separate from the plugin, where the plugin handles all of the UI, authN, pull/edit/commit/push workflow in however way is best for that specific VCS provider