While some GitHub Actions always run from main depending on the trigger, others may run from the base branch which, for long-lived feature branches, may be stale. For this and related reasons, we should add a workflow that is less aggressive than GitHub's "require branches be up to date" when merging, but still a required check that requires some amount of freshness on typical PR triggers like creation and updates (pushes).
For example, when merging into a branch you can be no more than N commits behind. If that base branch is not main (or the default, in general), also require merging main into the base branch. Or something like that.
While some GitHub Actions always run from
maindepending on the trigger, others may run from the base branch which, for long-lived feature branches, may be stale. For this and related reasons, we should add a workflow that is less aggressive than GitHub's "require branches be up to date" when merging, but still a required check that requires some amount of freshness on typical PR triggers like creation and updates (pushes).For example, when merging into a branch you can be no more than N commits behind. If that base branch is not
main(or the default, in general), also require mergingmaininto the base branch. Or something like that.