REF: q2-fmt ci

[cherman2]

Following dwq2 How-Tos on how to implement CI and GHA for weekly testing

[lizgehret]

overall this lgtm @cherman2! one small inline change to your README for your environment name and this should be ready for merge.

the only thing i noticed (that i'm assuming you did intentionally) is that your env files for 2024.10 and dev are targeting identical channels (2024.10/amplicon/passed) - i don't think it matters, but you could probably consolidate to just the dev env. I don't have strong feelings either way, so you can take that suggestion or leave it as-is!

[cherman2]

Thanks @lizgehret!
You are right that currently those are duplicates. I guess I kinda thought of this as creating a system. Like once .10 is release I will change the env file to use 2024.10/released and I will bump my dev on to use 2025.4/passed. Then I will start making the env files per release like suggested. I would have done a 2024.5 env but q2-fmt wont build there becuase of stats.

Will you do the mergonors (merge honors)?

[lizgehret]

Roger that, makes sense to me @cherman2!

lgtm!! 🚀