[Bug]: Run CI GitHub Action On Changes To Pull Request

[TimothyWillard]

Label

bug, gempyor, meta/workflow

Priority Label

high priority

Describe the bug/issue

The unit tests for gempyor will pull files from the examples/tutorials/ folder by the gempyor CI GitHub action which can cause configs that break CI to be introduced silently. See 7d10aa1.

To Reproduce

1. Modify files in the examples/tutorials/ directory.
2. Open a PR with those changes.
3. Note that the gempyor CI action does not run.

Environment, if relevant

Not relevant

[TimothyWillard]

This is a misunderstanding on my part, the gempyor CI action does run on changes to the examples:

flepiMoP/.github/workflows/gempyor-ci.yml

Lines 3 to 16 in f680be3

	on:
	workflow_dispatch:
	push:
	paths:
	- examples/**/*
	- flepimop/gempyor_pkg/**/*
	branches:
	- main
	pull_request:
	paths:
	- examples/**/*
	- flepimop/gempyor_pkg/**/*
	branches:
	- main

The issue in GH-407 was the PR was originally targeted for main and the changes didn't affect the unit tests in main so the action ran fine on f7d19eb. Then the PR target was changed to dev which included tests that were affected and the action was not ran again because no commits were added. We would have caught this if the PR was targeted for dev from the beginning or if any commits were added after changing the target. I think the solution is to add explicit types to the pull_request trigger of ["edited", "opened", "synchronize", "reopened"]. See https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#pull_request for details.