first of all, thanks for the great tool!
Since tinkering around with komodo, i stumble often about a specific problem with the repos.
I added a github repo to komodo and configured an "on clone" and "on pull" action. So far so good.
When cloning the repo, the clone action gets executed from the repo root. -> works as desired. After, a pull is executed and it works the same.
BUT
Later, when I only "pull" the repo (e.g. triggered via webhook), the path for the "on pull" action is not the repo root but the "repos" root folder:
to circumvent this, i can add the repo name as "path" to the "on pull" command and it works again. Unfortunately, this causes the clone to break since it tries to execute the "on pull" withe the correct base:
As you can see, when cloning (and the pull action get's triggered), the "added" path gets added to the repo root and does obviously not exist.
So I have to clean it like it should to clone and add the repo name in the "on pull" path after to pull afterwards.
Originally created by @mirisbowring on GitHub (Jun 4, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/580
Hi,
first of all, thanks for the great tool!
Since tinkering around with komodo, i stumble often about a specific problem with the repos.
I added a github repo to komodo and configured an "on clone" and "on pull" action. So far so good.
When cloning the repo, the clone action gets executed from the repo root. -> works as desired. After, a pull is executed and it works the same.
BUT
Later, when I only "pull" the repo (e.g. triggered via webhook), the path for the "on pull" action is not the repo root but the "repos" root folder:
<img width="850" alt="Image" src="https://github.com/user-attachments/assets/1acae668-ab49-4972-b7c4-238e2ca606db" />
to circumvent this, i can add the repo name as "path" to the "on pull" command and it works again. Unfortunately, this causes the clone to break since it tries to execute the "on pull" withe the correct base:
<img width="1083" alt="Image" src="https://github.com/user-attachments/assets/035d7c0c-8803-47af-910e-ff782261b73b" />
As you can see, when cloning (and the pull action get's triggered), the "added" path gets added to the repo root and does obviously not exist.
So I have to clean it like it should to clone and add the repo name in the "on pull" path after to pull afterwards.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @mirisbowring on GitHub (Jun 4, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/580
Hi,
first of all, thanks for the great tool!
Since tinkering around with komodo, i stumble often about a specific problem with the repos.
I added a github repo to komodo and configured an "on clone" and "on pull" action. So far so good.
When cloning the repo, the clone action gets executed from the repo root. -> works as desired. After, a pull is executed and it works the same.
BUT
Later, when I only "pull" the repo (e.g. triggered via webhook), the path for the "on pull" action is not the repo root but the "repos" root folder:
to circumvent this, i can add the repo name as "path" to the "on pull" command and it works again. Unfortunately, this causes the clone to break since it tries to execute the "on pull" withe the correct base:
As you can see, when cloning (and the pull action get's triggered), the "added" path gets added to the repo root and does obviously not exist.
So I have to clean it like it should to clone and add the repo name in the "on pull" path after to pull afterwards.
@mbecker20 commented on GitHub (Jun 6, 2025):
I noticed recently as well, I have a note to fix