Closed pasrom closed 7 months ago
Hi @pasrom !
The above patch should solve the problem. It will change origin/main to origin_main.
You can try using v2_dk7 instead of v2_k7
Note: When I tried your repo locally I was able to use either origin/main and main. But this could be related to what git uses as default source.
@set-soft, thanks for the quick fix!
Tried the v2_dk7
tag and it worked like a charm.
Thanks again!
Bug Description
When enabling
add_link_id
and using thebasic_diff_pcb
orbasic_diff_sch
output, an error occurs indicating a missing file. The error message is: Steps to Reproduce
This issue was encountered with the following
.kibot.yaml
configuration: kibot config (PR: https://github.com/e-battery-systems/bms-c1-tests/pull/6).Expected Behavior
The expected behavior is consistent with the functionality in GH-action tag
v2_k7_1_6_3
, where the described error does not occur (GH action run). Image used:ghcr.io/inti-cmnb/kicad7_auto_full:latest@sha256:cd92486f6f295074ce4b7d09bc3a4d39b271fa31235600bfa70400c958aea6f6
Environment Details
INTI-CMNB/KiBot@v2_k7
.Image used:
ghcr.io/inti-cmnb/kicad7_auto_full:latest@sha256:bb5e5319e5ba22d560e28a69b89c8cfd587474b9574314f3f678dcbff376f621
Additional Information
This bug may have been introduced in recent commits, particularly [Diff][Fixed] Problems when trying to use an already existent worktree and [Diff][Fixed] Worktree's can leave junk branches, which impacted how branches are specified (
origin/main
vs.main
) and led to link creation failures whenadd_link_id
istrue
. The issue arises from a modification in branch specification requirements; where previously referring to a branch simply asmain
was adequate, it is now necessary to explicitly useorigin/main
. As a result, utilizingorigin/main
in combination withadd_link_id: true
disrupts the link creation process.