-
Notifications
You must be signed in to change notification settings - Fork 6
Issues with branches and pico updating them #76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is probably because pico receives the event from gitwatcher and then uses the URL to find the relevant target. It should use the url and branch name, or maybe even the path. |
Problematic function: Line 277 in 3dee36d
|
|
I think path makes the most sense to do. |
so something like this?
With the watcher event passing in |
On second thought, the target struct needs to keep track of the directory it is in, since there is no way to get the full path from just using |
For some reason when Pico see's changes in a repo, it somehow manages to run for all repos of the same url even if they have different branches.
For example today, I pushed to my development branch, and CI passed and pushed a staging container, well what happened was that the production server went down and it seems pico was responsible for doing that.
The production repo should not have been touched at all, since no event changes happened to that branch.
The text was updated successfully, but these errors were encountered: