Mislav Marohnić
Mislav Marohnić
@bwoodsend I'm looking, but so far I do not see the fix included in any specific GHES versions.
> Arguably the most frustrating part of the `gh` command. If it is aware enough to present me with all the possible fields in the schema, it is smart enough...
@ringerc If the goal is to view information about the latest Release, with gh this is possible right now: ``` gh release view --json tagName { "tagName": "v2.21.2" } ```
@stevehipwell Could you illustrate what you mean with an example? To be clear, I still support adding generic `gh release list --json ...` support to the command. However, until that...
When `gh release list` output is redirected to a file or a script, it outputs the columns in a tab-separated format. I see no added value in encoding exactly the...
There is an open PR that adds this feature that you are all welcome to try out! Due to the size of added code, our team didn't yet time to...
@oneandonlymike `issue list` to my knowledge does not support any features related to Projects. But if you find a gh command where new-style Projects are not yet supported (but should...
Update: the platform team just shipped a new API to revert a PR with: ```graphql mutation ($pr: ID!, $asDraft: Boolean = false, $title: String, $body: String) { revertPullRequest( input: {...
@5HT2: that's a good point. A new command `revert` it is then 👍
Work prioritization looks like this: if something is tagged `help wanted`, that means that there should be enough information in the thread for an outside contributor to pick up the...