Repository navigation
Usage
Ian edited this page Nov 1, 2026
·
4 revisions
For the python script, please refer to that version's README.
For the GitHub action, nothing is finalized yet, but consider this example workflow job:
compose:
runs-on: ubuntu-latest
needs: build
steps:
- uses: actions/checkout@v7.0.1
with:
path: 'Piper-J3'
- uses: actions/download-artifact@v8.0.1
with:
path: tmp
- run: |
mv Piper-J3/.parcelignore .parcelignore
rm -r Piper-J3/plugins/J3/*_x64
mkdir Piper-J3/plugins/J3/lin_x64
mkdir Piper-J3/plugins/J3/win_x64
mkdir Piper-J3/plugins/J3/mac_x64
mv tmp/lin_x64/* Piper-J3/plugins/J3/lin_x64
mv tmp/win_x64/* Piper-J3/plugins/J3/win_x64
mv tmp/mac_x64/* Piper-J3/plugins/J3/mac_x64
rm -r tmp
- uses: slimit75/Parcel@v3.0.0-b1
with:
acf-in-name: 'Piper-J3'This job assumes that the previous job has compiled the aircraft plugin for all platforms and uploaded them as artifacts, like so in this example:
- uses: actions/upload-artifact@v7.0.1
if: runner.os == 'Linux'
with:
name: lin_x64
path: plugins/J3/lin_x64
- uses: actions/upload-artifact@v7.0.1
if: runner.os == 'Windows'
with:
name: win_x64
path: plugins/J3/win_x64
- uses: actions/upload-artifact@v7.0.1
if: runner.os == 'macOS'
with:
name: mac_x64
path: plugins/J3/mac_x64