Describe the feature or problem you’d like to solve

b/c this information isn't available as, e.g. a --json input, the only way to get it is w/ the gh api command

the field is marshaled here, but never stated to be a field.

additionally, the field as it currently is is named "Attempts" which, due to being plural, eludes to the idea that this field represents "how many attempts have been done of this run" rather than what it really represents: which attempt this run is, i.e. if "1", it was the first attempt, "2" is the 2nd, etc.

Proposed solution

expose the field as attempt

Thanks for creating this @cawfeecake. I agree with everything you said but I'm still curious what you are actually using this for? This kind of information really helps us when we look at how our community use the CLI and how we should steward it in the future.

I've labelled this help wanted though I understand you already have a PR open, it's just a way for us to keep track of issues that we aren't working on ourselves.

what you are actually using this for?

i believe i ran into this issue when i was researching run outcomes, and i went to try to list runs (gh run ls --json) and filter down to just the runs that had been attempted more than once. that's when i discovered that the information wasn't an available --json field. however, it is accessible via a gh api call, so it feels like users should be able to get that information thru the comfortable gh run command group. additionally, i have seen that in the past there have been PRs here with this same goal of exposing more information in a command group that is currently only accessible thru the gh tool by writing a gh api command.