Record pystats periodically.

[mdboom]

Part of faster-cpython/tools#115

[ericsnowcurrently]

LGTM

How is this triggered?

[mdboom]

Sorry -- I should make this a draft. The plan is this will be a weekly cron action, but I have it set to pull_request right now so I can test it. It's broken by python/cpython#99701 at the moment.

[brandtbucher]

Thanks for working on this! This will be a big win for our workflow (I was just trying to decide if it's worth doing a local stats run today to check up on 3.12).

[mdboom]

This should be working now, and it would be good to get a review in case anything in the action isn't clear (@ericsnowcurrently, @brandtbucher). There is no way to fully test the part that adds results to the ideas repo until we merge this and let the job run -- I think we just have to merge and cross our fingers. (Pull requests don't have permissions to add files to the repo, for obvious reasons).

You can see the example output here: https://github.com/faster-cpython/ideas/suites/9543557905/artifacts/453779401

[ericsnowcurrently]

LGTM

I'm not especially familiar with the structure and semantics of GitHub workflow configs, but what you have made sense and nothing jumped out at me as wrong. 🙂