[GH-ISSUE #634] Cannot push a stack change to non-main branch with git repo #2326

New Issue

GiteaMirror · 2026-04-11T10:15:14-05:00

GiteaMirror commented

2026-04-11 10:15:14 -05:00

Originally created by @Chuckame on GitHub (Jun 28, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/634

Issue

When having a stack from a git repository with a non main branch, it doesn't work.

Error message during push:

command

cd /etc/komodo/repos/<the repo name> && git push --set-upstream origin main

stderr

error: src refspec main does not match any
error: failed to push some refs to 'https://github.com/Chuckame/<the repo name>'

I've configured master but it still uses main

To reproduce

Create a repository and set a branch name to something else than main
create a stack from a git repository
Start the stack
Then make a change in the docker compose file
Then save -> Here it fails 💥

Originally created by @Chuckame on GitHub (Jun 28, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/634 # Issue When having a stack from a git repository with a non `main` branch, it doesn't work. Error message during push: ``` command cd /etc/komodo/repos/<the repo name> && git push --set-upstream origin main stderr error: src refspec main does not match any error: failed to push some refs to 'https://github.com/Chuckame/<the repo name>' ``` I've configured `master` but it still uses `main` # To reproduce - Create a repository and set a branch name to something else than `main` - create a stack from a git repository - Start the stack - Then make a change in the docker compose file - Then save -> Here it fails 💥

GiteaMirror added the 1.19.2 bug labels 2026-04-11 10:15:14 -05:00

GiteaMirror closed this issue

2026-04-11 10:15:14 -05:00

GiteaMirror commented

2026-04-11 10:15:16 -05:00

@Dlotan commented on GitHub (Jun 29, 2025):

did you try redeploy first? I had this problem and a workaround was to do a redeploy before being able to make changes from komodo

@Dlotan commented on GitHub (Jun 29, 2025): did you try redeploy first? I had this problem and a workaround was to do a redeploy before being able to make changes from komodo

GiteaMirror commented

2026-04-11 10:15:16 -05:00

@ridvan-cln commented on GitHub (Jul 13, 2025):

did you try redeploy first? I had this problem and a workaround was to do a redeploy before being able to make changes from komodo

Not OP but i have the same issue, redeploy does not fix it for me.

@ridvan-cln commented on GitHub (Jul 13, 2025): > did you try redeploy first? I had this problem and a workaround was to do a redeploy before being able to make changes from komodo Not OP but i have the same issue, redeploy does not fix it for me.

GiteaMirror commented

2026-04-11 10:15:17 -05:00

@hillbicks commented on GitHub (Aug 8, 2025):

Yes, same here. I cloned a github repo to my forgejo instance (branch master), added the repo in komodo and then added the stack. Go to info tab to make changes, for example change a port that is already used in another container. You can't deploy the stack because the deploy fails without being able to make the changes.

I think komodo should also take the branch from the repo config and not assume the branch name to be main.

@hillbicks commented on GitHub (Aug 8, 2025): Yes, same here. I cloned a github repo to my forgejo instance (branch master), added the repo in komodo and then added the stack. Go to info tab to make changes, for example change a port that is already used in another container. You can't deploy the stack because the deploy fails without being able to make the changes. I think komodo should also take the branch from the repo config and not assume the branch name to be main.

GiteaMirror commented

2026-04-11 10:15:18 -05:00

@mbecker20 commented on GitHub (Aug 29, 2025):

Tracked down the issue and the linked commit should fix it. It will be included in 1.19.2 (likely Sunday)

@mbecker20 commented on GitHub (Aug 29, 2025): Tracked down the issue and the linked commit should fix it. It will be included in 1.19.2 (likely Sunday)

GiteaMirror commented

2026-04-11 10:15:18 -05:00

@mbecker20 commented on GitHub (Sep 1, 2025):

Hi, v1.19.2 is now out and this issue should now be fixed for Stacks, Builds, and Resource Syncs which use Linked Repos.

@mbecker20 commented on GitHub (Sep 1, 2025): Hi, v1.19.2 is now out and this issue should now be fixed for Stacks, Builds, and Resource Syncs which use Linked Repos.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#2326