mirror of
https://github.com/moghtech/komodo.git
synced 2026-05-07 10:53:18 -05:00
[Feature] Add option to sync Repositories back to git. #60
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/komodo#60
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @arevindh on GitHub (Sep 14, 2024).
Currently, the Repositories section provides users with three key options:
I believe that the addition of a Push button would be highly beneficial to the overall user experience. This button would allow users to easily synchronize their local changes back to the remote Git repository, streamlining the workflow and reducing the need for manual Git commands.
@mbecker20 commented on GitHub (Aug 26, 2025):
If you are making change in the repo being cloned by Komodo, surely you can commit and push from there, or edit the repo from another device and push. Theres lots of options as to what files to include in the commit, the commit message, etc. The purpose of this resource is to pull and execute on Servers and I believe this feature to be out of scope.
@mbecker20 commented on GitHub (Aug 30, 2025):
I think its a fair feature request, I can actually see some use cases such as keeping a silverbullet repo pushed up to git automatically.
@serfriz commented on GitHub (Sep 5, 2025):
I think this would be a great feature. I believe a lot of people (including me) are using the repos functionality as a way to clone an existing docker compose repository, and then use the stacks "files on server" mode to actually deploy/edit the docker compose and .env files (instead of using the stacks "git repo" mode). By doing it this way the structure of all docker compose files is maintained, otherwise the repository gets cloned with every new stack (an OCD trigger for many 😅).
Obviously if any change to the docker compose files is done through Komodo, it would be great to have a button to commit all changes with an optional message (respecting the git ignore rules).
@mbecker20 commented on GitHub (Sep 5, 2025):
@serfriz This is no longer the case. You can now "link" Stacks directly to Repos. If multiple Stacks are on the same Server, and linked to same Repo, the folder will be cloned once to the host and each Stack will use the same folder. No more multiple clones of same repo folder.
Note that by default the repo folder will be cloned at $root_directory/repos/<repo_name>. You can change this by setting Clone Path on the (Komodo) Repo config:
More info: https://github.com/moghtech/komodo/releases/tag/v1.18.2
@serfriz commented on GitHub (Sep 6, 2025):
That's great! Sorry I missed the feature update, maybe it could be made a bit more clear in the documentation (including the part that a new repo doesn't need to be linked to a host) since there are plenty of blog entries and reddit posts that reference the previous behavior.