Add build-only GHA workflows for missing devices #61

	name: Raspberry Pi 4 (using 64bit OS)

	on:
	# With these triggers the Yocto jobs will run
	# in parallel with the Flowzone jobs, which is fine for now
	# and allows us to better control what we want to test and when.
	# It is expected that Flowzone could fail, but yocto jobs will run.
	pull_request:
	branches:
	- "main"
	- "master"
	pull_request_target:
	branches:
	- "main"
	- "master"

	jobs:
	yocto:
	name: Yocto
	# FIXME: This workflow has dependencies on scripts in the balena-yocto-scripts repository
	# which is pinned separately as a submodule in the device repo. Expect some drift but try to retain compatibility.
	uses: balena-os/balena-yocto-scripts/.github/workflows/[email protected]
	# Prevent duplicate workflow executions for pull_request (PR) and pull_request_target (PRT) events.
	# Both PR and PRT will be triggered for the same pull request, whether it is internal or from a fork.
	# This condition will prevent the workflow from running twice for the same pull request while
	# still allowing it to run for all other event types.
	if: (github.event.pull_request.head.repo.full_name == github.repository) == (github.event_name == 'pull_request')
	secrets: inherit
	with:
	machine: raspberrypi4-64
	# Needed for testing - defaults to production
	environment: balena-staging.com
	device-repo: balena-os/balena-raspberrypi
	device-repo-ref: master
	# Pin to the current commit
	meta-balena-ref: ${{ github.sha }}
	# Don't deploy any artifacts for meta-balena build sanity workflows
	deploy-s3: false
	deploy-hostapp: false
	deploy-ami: false

Provide feedback