Awkward mixture of yes/no & true/false inputs

[IanButterworth]

julia-runtest/action.yml

Lines 9 to 34 in 9b1be2f

	inputs:
	check_bounds:
	description: 'Value determining which bounds checking setting to use. Options: yes | no | auto. Default value: yes.'
	default: 'yes'
	coverage:
	description: 'Value determining whether to test with coverage or not. Options: true | false. Default value: true.'
	default: 'true'
	depwarn:
	description: 'Value passed to the --depwarn flag. Options: yes | no | error. Default value: yes.'
	default: 'yes'
	force_latest_compatible_version:
	description: 'If true, then, for each [compat] entry in the active project, only allow the latest compatible version. If the value is auto and the pull request has been opened by Dependabot or CompatHelper, then force_latest_compatible_version will be set to true, otherwise it will be set to false. Options: true | false | auto. Default value: auto.'
	default: 'auto'
	inline:
	description: 'Value passed to the --inline flag. Options: yes | no. Default value: yes.'
	default: 'yes'
	prefix:
	description: 'Value inserted in front of the julia command, e.g. for running xvfb-run julia [...]'
	default: ''
	required: false
	project:
	description: 'Value passed to the --project flag. The default value is the repository root: "@."'
	default: '@.'
	annotate:
	description: 'Whether or not to attempt to create GitHub annotations to show test failures inline. Only effective on Julia 1.8+.'
	default: 'false'

We should probably pick one style and deprecate the old values.

I wonder if there's a general style guide for this for github actions.