diff --git a/docs/docs/development/contributing-boards.md b/docs/docs/development/contributing-boards.md index 49a65722d..3bc53f07e 100644 --- a/docs/docs/development/contributing-boards.md +++ b/docs/docs/development/contributing-boards.md @@ -13,7 +13,7 @@ The community support boards framework allows a user in the community to be the ## Getting Started -1. Follow the steps from [the main contributing docs](/development/contributing.md). +1. Follow the steps from [the main contributing docs](development/contributing.md). 2. Create a new build type under `docker/` 3. Get build working as expected, all board-specific changes should be done inside of the board specific docker file. @@ -72,17 +72,17 @@ COPY --from=rootfs / / The images for each board will be built for each Frigate release, this is done in the `.github/workflows/ci.yml` file. The board build workflow will need to be added here. ```yml - - name: Build and push board build - uses: docker/bake-action@v3 - with: - push: true - targets: board # this is the target in the board.hcl file - files: docker/board/board.hcl # this should be updated with the actual board type - # the tags should be updated with the actual board types as well - # the community board builds should never push to cache, but it can pull from cache - set: | - board.tags=ghcr.io/${{ steps.lowercaseRepo.outputs.lowercase }}:${{ github.ref_name }}-${{ env.SHORT_SHA }}-board - *.cache-from=type=gha +- name: Build and push board build + uses: docker/bake-action@v3 + with: + push: true + targets: board # this is the target in the board.hcl file + files: docker/board/board.hcl # this should be updated with the actual board type + # the tags should be updated with the actual board types as well + # the community board builds should never push to cache, but it can pull from cache + set: | + board.tags=ghcr.io/${{ steps.lowercaseRepo.outputs.lowercase }}:${{ github.ref_name }}-${{ env.SHORT_SHA }}-board + *.cache-from=type=gha ``` ### Code Owner File