Deduplicate CI spam

[JacobCoffee]

Description

• removes multiple runs in PRs. we still run on merge, and in PRs but we dont run twice in PRs
• pulls migrations checkk into its own step
• spaces are freee

before:

after:

[hugovk]

I'd still like to be able to run the CI on feature branches in my fork, before opening PRs.

Can we configure it to still allow that?

[JacobCoffee]

@hugovk i think that would be enabled on the fork right? or do i need to add a workflow_dispatch for ci.yml?

[hugovk]

Well, first of all the fork owner has to click a button to enable the CI on forks. This is a one-time thing, and they can disable later if they want.

But we also need to make sure the YAML config in the repo doesn't prohibit it from running.

I suggest we keep on: [push, pull_request, workflow_dispatch] at the top. (It can be handy to have workflow_dispatch there, you never know when you want to manually trigger via the UI.)

And then add this for each job:

jobs:
  test:
    if: github.event_name != 'push' || github.event.repository.fork == true

So these will trigger:

• upstream: only PR and manual trigger
• fork: everything

[hugovk]

Looks good! Will also confirm after merge :)

[hugovk]

Looking good on my side 👍