Joseph Langley

> it's not just all about the milestones; sometimes patches come in via email or things can get commited directly to master. > > How do you anticipate handling those...

Flex previously used TravisCI. The first bunch of commits in this PR translate that pipeline to GitHub Actions as much as possible. I can split that chunk out from automated...

I've split the migration to Github Actions out to PR #523. I'll rebase or replace this PR once that one is dealt with.

Rebased the automated release actions after splitting out the codeQL and distcheck actions. Also switched to 'sed -i' as suggested. (I'll handle matrix builds in the build action a little...

> There's currently no CI generated tarball, is it? > > If not then can we get it first (making the result of passing `make distcheck` available (and before running...

> Some people use one key for nightly builds and another for releases, the first used for manual verification, the second also in distributions. Totally supportable. Just looks like a...

I thought we'd handled this already. PR is in flight.

Flex uses m4 at runtime as well as build time. The build process tries to use your system's m4 installation and after install. You can set the M4 variable in...

Amending my answer from 2021-01-30: Flex's build system uses your default m4 unless you tell it otherwise. That default m4 is just whatever ./configure can find. After install, flex tries...

A couple of PRs that will make this possible are in the pipeline. It's been a challenge in the past because so much C was emitted from Flex's compiled code....