[Added] Example using dev branch

Author: set-soft

.github/workflows/test_using_dev.yml

@@ -0,0 +1,104 @@
+name: Simple KiBot CI/CD test (dev)
+
+# Controls when the action will run. Triggers the workflow on push or pull request
+# events but only for the master branch
+# If any of the listed file changes we run the workflow
+on:
+  push:
+    paths:
+      - 'kicad_ci_test.kicad_sch'
+      - 'kicad_ci_test.kicad_pcb'
+      - 'kicad_ci_test.kibot.yaml'
+      - '.github/workflows/test1.yml'
+  pull_request:
+    paths:
+      - 'kicad_ci_test.kicad_sch'
+      - 'kicad_ci_test.kicad_pcb'
+      - 'kicad_ci_test.kibot.yaml'
+      - '.github/workflows/test1.yml'
+  schedule:
+    # Run on Wednesday @ 5:43 to keep the artifacts alive
+    - cron: '43 5 * * 3'
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  ERC:
+    runs-on: ubuntu-latest
+    # Here use kicad8_auto:latest if you don't need all features, i.e. Blender render
+    # You can use ghcr.io/inti-cmnb/kicad8_auto_full:dev to get the last fixes
+    # In this case change "8" by the KiCad you need. Also don't forget to change this tag
+    # once your project is finished, pointing to a stable KiBot release
+    # Use the same for all steps
+    container: ghcr.io/inti-cmnb/kicad8_auto:dev
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Run ERC
+      run: |
+        [ -f *.kicad_sch ] && kibot  -d Fabrication -s update_xml,run_drc -i
+
+    - name: Retrieve results
+      uses: actions/upload-artifact@v4
+      with:
+        name: ERC_Output
+        path: Fabrication
+
+  DRC:
+    runs-on: ubuntu-latest
+    container: ghcr.io/inti-cmnb/kicad8_auto:dev
+    needs: ERC
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Run DRC
+      run: |
+        [ -f *.kicad_pcb ] && kibot  -d Fabrication -s update_xml,erc -i
+
+    - name: Retrieve results
+      uses: actions/upload-artifact@v4
+      with:
+        name: DRC_Output
+        path: Fabrication
+
+  FabSch:
+    name: Schematic fabrication files
+    runs-on: ubuntu-latest
+    container: ghcr.io/inti-cmnb/kicad8_auto:dev
+    needs: ERC
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Run schematic stuff
+      run: |
+        [ -f *.kicad_sch ] && kibot  -d Fabrication -s drc,erc print_sch bom_html
+
+    - name: Retrieve results
+      uses: actions/upload-artifact@v4
+      with:
+        name: FabSch_Output
+        path: Fabrication
+
+  FabPCB:
+    name: PCB fabrication files
+    runs-on: ubuntu-latest
+    # Here we need Blender so we use the full image
+    container: ghcr.io/inti-cmnb/kicad8_auto_full:dev
+    needs: DRC
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Run PCB stuff
+      run: |
+        [ -f *.kicad_pcb ] && kibot  -d Fabrication -s all print_front gerbers _blender_3d_top
+
+    - name: Retrieve results
+      uses: actions/upload-artifact@v4
+      with:
+        name: FabPCB_Output
+        path: Fabrication
+
+

README.md

@@ -95,3 +95,11 @@ Another detail is how to checkout the submodules. One option is to use the *subm
       with:
         submodules: 'true'
 ```
+
+
+## Example using development images
+
+Sometimes a bug in KiBot might prevent using it. In this case report it [here](https://github.com/INTI-CMNB/KiBot/issues).
+
+Once the bug is fixed you can use the dev (development) docker images. You just need to chage *latest* by *dev*
+The following example shows it: [.github/workflows/test_using_dev.yml](https://github.com/INTI-CMNB/kicad_ci_test/blob/master/.github/workflows/test_using_dev.yml)