Research inquiry: Ruff’s release approval workflow

[abishekgiri]

Hello Ruff maintainers,
I’m studying whether information available before approval of a protected release job can predict whether the subsequently approved job succeeds or fails.
Your release guide describes an approval step before publication. Could you point me to the person responsible for that workflow? I’d like to ask whether it qualifies for a small passive observational study and whether they’d be willing to discuss metadata collection.
Initially, I only need a brief conversation about the approval process, release frequency, and whether job failures/timeouts are recorded. No source-code contents, secrets, production access, or changes to release decisions are requested.
Thank you,
Abishek Kumar Giri

[MichaReiser]

I’m studying whether information available before approval of a protected release job can predict whether the subsequently approved job succeeds or fails.

It's not clear to me how that would be possible.

You can collect any public available metadata using GitHub's API but don't want to change our release pipeline to run custom code or collect additional metadata.