name: example
on:
push:
paths:
- '**.sch'
- '**.kicad_pcb'
pull_request:
paths:
- '**.sch'
- '**.kicad_pcb'
jobs:
example:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: stopstopstop/kicad-action@master
with:
# Required - kibot config file
config: docs.kibot.yaml
# optional - prefix to output defined in config
dir: docs
# optional - schematic file
schema: '*.sch'
# optional - PCB design file
board: '*.kicad_pcb'
- name: upload results
uses: actions/upload-artifact@v2
with:
name: docs
path: docs
The predefined configs do run a ERC and DRC in advance, if these checks fail no exports will be generated. You could write your own config file and define filters to ignore these errors therefore forcing to export the data. In this case be careful not to end up with some faulty PCB.
⚠️ Pushing auto generated files back to the same branch you are working on manualy is a bad idea!
You need to have Docker installed.
git clone --recursive https://github.com/stopstopstop/kicad-action /some/where/kicad-exports
cd /some/where/kicad-exports
make && make install
go to your KiCad project folder and run kicad-exports
cd /my/kicad/example-project
kicad-exports -d $DIR_OUT -e $SCHEMA -b $BOARD -c $CONFIG
⚠️ running any command your git repository will be modified using kicad-git-filters
kicad-exports -c docs.kibot.yaml
place config file in directory of your kicad project and use relative path.
kicad-exports -c myconfig.kibot.yaml -v -s all
or run multiple config files
kicad-exports -c config/*.kibot.yaml -b myproject.kicad_pcb -e myproject.sch
bundles are a choice of configs run sequentially
kicad-exports -c $(echo $(cat config/bundle/documentation.default))
kicad-exports -x $COMMIT_HASH -b myproject.kicad_pcb
-v, --verbose
is useful while developing own config files-o, --overwrite key=value
overwrite variables in config file-s, --skip $arg
skips preflight from given config file-x, --diff $commit_hash
output differential files between $commit_hash and latest commit