William Martin

> It would be great to get fullDatabaseId into the output. It might be good to change the documentation to call the existing output node_id instead of just id as,...

## Acceptance Criteria **Given** there is a PR that exists with in **When** I run `gh pr view --repo --json number,fullDatabaseId ` **Then** I see a JSON document containing the...

Just to clarify my understanding of this issue there are two things going on. ### cat vs no cat When determining the repo that should be targeted for remote operations...

@kpprasa-gather >So this is still unresolved? We haven't done anything to change the network remote resolution, so yes this issue could still occur. > How come it works for some...

Unfortunately the [REST API does require the repo ID](https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2022-11-28#cancel-a-workflow-run) which is why the CLI needs to know the repo to which the run belongs. However, instead of initialising a git...

From my perspective this seems like a reasonable ask but I will defer to the @cli/codespaces team to weigh in on this, since it's their domain. It looks like there...

Hey @notomo, sorry this PR has sat without review for so long. Since it was opened both @mislav and @vilmibm left the company. I assigned it to myself to review...

Alright, thanks for resolving that. Just to give you a heads up, since this work was initially planned in #390, there has been additional discussion around delaying PR/Issue command improvements...

I have also added this PR to the list of improvements on the tracking issue.

Wow this is an oooooold issue. Thank you for your contribution. The details of the original issue look quite involved, so it may take me some time to fully grok...