While the `state` field corresponds 1:1 with different GitHub Actions
states, the `bucket` field is an abstraction of the CLI that lacked
documentation. This both adds documentation about the existence of the
`bucket` field and enumerates the possible values.
There are no code changes required to make this work. I added a test
specifying `<owner>/<number>` and nothing failed. Any syntax issues are
returned by the api with a generic message:
```
Invalid search query "project:\"<string>\" type:issue".
An invalid project was specified.
```
This, combined with the updated docstring, should be sufficient for users
to troubleshoot any issues with the `--project` flag syntax
There are no code changes required to make this work. I added a test
specifying `<owner>/<number>` and nothing failed. Any syntax issues are
returned by the api with a generic message:
```
Invalid search query "project:\"<string>\" type:pr".
An invalid project was specified.
```
This, combined with the updated docstring, should be sufficient for users
to troubleshoot any issues with the `--project` flag syntax
With the upcoming migration from v1 project to v2 projects, we'd like the
language in our documentation to align with v2 project language. In v2,
projects are referred to by `title` and not `name`, though they are
functionally equivalent under the hood for the CLI
Change logging of `gh repo set-default --view` to `stderr` when no default exists to better conform with expectations and unix standards.
---------
Signed-off-by: Prabhat <iprabhatdev@gmail.com>
This commit addresses the documentation issue.
The discussion at #7018 has confirmed that it is undocumented that
the current behavior of `gh run download` with `-n` and no `run-id`
downloads the latest artifact.
Although the behavior has not been created intentionally, it is the one
that should be documented and the future releases should warn before
a breaking change.
