Reusable workflows vs Actions, what should we do?

[dentarg]

Since #30 we have two ways to do CI

.github/workflows/ruby-ci.yml, a reusable workflow that defines the runner image (e.g. ubuntu-latest) and multiple jobs and their steps

actions/.github/workflows/ruby-ci.yml

Lines 1 to 4 in 2d0c6ac

	name: Ruby CI
	on:
	workflow_call:

84codes/actions/ruby-ci-setup, "just" a regular GitHub action that defines steps to run, the project using the action needs to define the runner image and the job and call the action from a step, but it allows the project to add their own steps to the job

actions/ruby-ci-setup/action.yml

Lines 1 to 8 in 2d0c6ac

	name: "Ruby CI Setup"
	description: "Setup PostgreSQL, LavinMQ, and Ruby environment for CI"
	author: "84codes"
	inputs:
	# Checkout inputs
	checkout:
	description: "If actions/checkout step should run or not"