Add CI workflows for testing PRs on release branches

az-digital / az_quickstart

UArizona's web content management system built with Drupal 10.

https://quickstart.arizona.edu

GNU General Public License v2.0

30 stars 20 forks source link

Add CI workflows for testing PRs on release branches #1282

Open joeparsons opened 2 years ago

joeparsons commented 2 years ago

Motivation

We need to be able to test whether a change works with our release branches before merging.

Proposed Resolution

Add CI workflows that are either automatically run against all of our supported release branches or can manually be run against specific branches.

Additional context

GItHub actions' matrix job strategy feature is probably useful for this.

joeparsons commented 2 years ago

Things that would be good to test on release branches (for PRs):

[ ] Verify composer install works (using scaffolding repo)
[ ] Run PHP unit tests (would require access to a headless google-chrome executable and chromedriver)
[x] Try running drush site:install (would require configuring MySQL on GH actions environment)

See .probo.yaml and .lando.yml configs for examples of how to run these.

trackleft commented 1 year ago

FYI for using a branch name as an alias for the currently installed version, you could do the following

export CURRENT_QUICKSTART_VERSION=`composer show az-digital/az_quickstart --format=json | jq -r '.versions[]'
composer require az-digital/az_quickstart "dev-${inputs.branchname} as $CURRENT_QUICKSTART_VERSION"

Or something similar