VACMS-17142: Update service content types post-Service Location migration #5811

	name: Set Tugboat Tests Pending
	on:
	- pull_request_target
	permissions:
	pull-requests: write
	checks: write
	contents: write
	statuses: write
	jobs:
	# Tugboat tests are not automatically set pending, even though they are
	# required in branch protection rules (see #10553).
	#
	# Therefore, a PR can inappropriately appear to be ready to merge if,
	# for instance, a composer.lock merge conflict prevents the Tugboat
	# preview from successfully building.
	#
	# This action sets these tests pending from an immediate GitHub Action
	# so that we can trust our automated code review processes more.
	set-tugboat-tests-pending:
	name: Set Tugboat Tests Pending
	runs-on: ubuntu-latest
	steps:
	- name: Checkout
	uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
	- name: Set status for Tugboat tasks.
	run: \|
	test_names=(
	va/tests/cypress
	va/tests/phpunit
	va/tests/content-build-gql
	va/tests/status-error
	)
	for test_name in "${test_names[@]}"; do
	gh api \
	--method POST \
	-H "Accept: application/vnd.github+json" \
	"/repos/${GITHUB_REPOSITORY}/statuses/${SHA}" \
	-f state='pending' \
	-f context="${test_name}";
	done;
	env:
	SHA: ${{ github.event.pull_request.head.sha }}
	GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Provide feedback