Track information from weekly run

[zsusswein]

From @gvegayon in #54:

For the future, I suggest having a workflow (or a job within existing workflows) that creates a GitHub issue for the run (e.g., weekly runs) and uses that for posting information. That could be the way in which Azure batch communicates it is done or whatnot. That could be an action for https://github.com/CDCgov/cfa-actions!

@gvegayon can you expand on this a bit more? How do you propose it would work and what kind of information do you think we'd want to include in a weekly issue?

[gvegayon]

How/where are you currently tracking discussions about weekly runs? I would do it as GH issues and have the workflow file instantiating them automatically; perhaps in the CDCent side?

[zsusswein]

We have a pretty involved process. We have a weekly review meeting with pdfs with figures for review. We're also talking about moving to a dashboard like the one scenarios has.

[gvegayon]

What I had in mind was mostly for keeping track of the runs programmatically, as well as any coding discussions associated with it (maybe)? It would be complementary to the review process you currently have.

[zsusswein]

I think I'm still not totally following but I'm intrigued! Maybe let's revisit post-#48? It sounds like a cool idea and I'm having trouble getting my head around how it would work and what it could track safely in public.